Windsock

Attach a citation to a diligence item substantiating its status — a report section, a digitized logbook page, an external link, or free text. kind ∈ report_section | logbook_page | link | text; reference is the section id / page id / URL / text.

Post a comment to a diligence checklist item's thread (e.g. rationale for a pass/fail, a question, or a finding). Comments are attributed to the caller and appear in the item's living thread.

Add a custom (or accepted-suggestion) item to a report's diligence checklist. Requires a title; optional category, guidance, critical flag, and value_impact { min, max }. Creates the checklist on first use.

How an aircraft is flown across seven flight categories (training, business, pleasure, etc.) relative to a comparable cohort. Useful for appraisal narratives, insurance underwriting, and validating seller claims about usage.

Forward-looking probability that an aircraft will fly little over the next ~180 days, as of a given date. Used to flag stagnant inventory, prioritize inspections, and risk-score collateral.

Aggregate registry census for a filter set: the total number of matching aircraft plus breakdowns by US state and by build year — in one call, without paging individual tails. Directly answers "how many Cessna R182s are registered in Oregon" (filter make_model_id + state, then read total_count / state_counts). Uses the same filter grammar as search_aircraft. Counts are computed over up to fleet_cap aircraft.

Generate a full Windsock verified value report (contemporary model only) from the same inputs as the windsock.ai valuation wizard. Creates a durable report owned by your account and queues PDF generation. Send the tail AND everything you know about the aircraft: any aircraft_info field you omit is filled with the make/model cohort MEDIAN, so a report built from a year alone prices like an average example — the response's inputs.stats_imputed / inputs.year_imputed list what was filled. Requires Windsock PRO or Enterprise.

Remove one item from a report's diligence checklist (soft delete). Progress counters are recomputed automatically.

Everything an aviation underwriter checks about one aircraft, in one call: the value with calibrated ranges (likely = 68%, outer = 90%) and the model release that produced it; an optional hull-value check of an insured value against those ranges; the registration record (status, expiry, state, owner tenure, registrant changes — never owner names or addresses); airworthiness context (the type's ADs and STC count, accident, NTSB and service-difficulty record counts); and recent ADS-B activity with the 180-day low-activity probability. Provide a tail number OR make_model_id plus aircraft_info.year. Returns an enrichment_id that get_underwriting_enrichment re-serves exactly later. Fleet Command and Enterprise API tiers only.

Run enrich_aircraft_for_underwriting over a carrier's hull schedule of up to 100 aircraft and list the insured values outside the calibrated ranges: summary.outside_range holds the aircraft insured above the central range (direction over) or below it (direction under). Each item takes the same fields as enrich_aircraft_for_underwriting (registration or make_model_id + aircraft_info.year, insured_value, reference, ...). Set book_total to true to also get the schedule's expected dollar total and a 90% range for that total, tested on held-out books (it ran wide for large mixed books and narrow for books concentrated in one segment); values without calibrated ranges (for example reference-based values) are left out and listed in book_total.excluded. Fleet Command and Enterprise API tiers only; metered per aircraft.

Annual/monthly operating-cost breakdown for a specific tail, combining registry data, recent flight patterns, and optional override assumptions (fuel, insurance, hangar, annual hours, etc.). Great for pre-buy disclosures and TCO comparisons.

Canonically similar aircraft (same make/model cohort and equipment profile) to a given tail — for comp tables, substitute inventory, and "aircraft like this" lists. Comps stay on the ANCHOR'S OWN REGISTER by default: a US tail gets US comps, a Canadian tail Canadian ones. That matters because this registry spans 17 international registers — before scoping, a US Robinson R44 drew 14 of its 100 comps from foreign registers, which are different markets under different airworthiness authorities and not substitutes a US buyer can act on. Pass registry_scope="all" only when the caller genuinely wants the global fleet.

Forward avgas/jet fuel price projection for an airport over 1–15 day horizons, with uncertainty bands. For trip budgeting and FBO economics.

Generate the make/model-specific pre-buy diligence checklist for a report (frontier-model research grounded in real ADs/STCs). Idempotent: an already-generated checklist is returned as-is. Generation runs in the background; poll get_diligence_checklist / get_diligence_progress for status.

The authenticated account's tier, included quotas, current-month usage, and estimated cost. Use to check entitlements before firing paid tools.

How one portfolio aircraft is being flown: weekly flying days against its seasonal expectation, local/pattern vs. cross-country mix, and detected changes in utilisation or use. available is false when no profile exists yet.

Web pages found about one portfolio aircraft (for-sale posts, rental/charter use, accident reports, …), grouped into episodes by the question they answer and ranked alert / warn / info / history, each with its sources. Also lists the aircraft's records from before its acquisition.

Combined current weather (METAR) and forecast (TAF) for an airport by ICAO/ident — for trip planning context.

The avionics id to price map behind equipment-adjusted valuations: average catalogue price per unit plus the wholesale factor. Use it to value a specific aircraft's panel from its avionics ids — wholesale = sum(average_price over the aircraft's ids) * wholesale_factor. Pair with search_avionics to resolve panel text to ids.

Fetch the pre-buy diligence checklist header for a report: generation status, progress counters, and knowledge score. Returns an exists:false shape if no checklist has been generated yet (call generate_diligence_checklist to create one).

Fetch the gamified progress payload for a report's diligence checklist: percent complete, knowledge score, counters by state, critical-items-verified, and how many items were auto-verified from logbook records.

Suggest additional pre-buy checklist items for a report's diligence checklist: real Airworthiness Directives / STCs for the make/model that are not yet on the checklist, plus anonymized items other buyers have added for similar aircraft. Add one with add_diligence_item (source: "rag").

Historical actuals and optional forward forecast (with 75/95/99% confidence bands) for a named market metric, optionally scoped to an aircraft segment. Provides market context to complement individual valuations.

One portfolio aircraft in full: latest value, its 60-month value series, key facts, tracking status, estimated loan balance and LTV, and share of the fleet's value. holding.imputed_fields names the facts Windsock filled in (estimated, or from the FAA registry) rather than the holder provided, and holding.unknown_fields the ones the holder cleared; every other fact is the holder's own. Also answers for an aircraft that has left the portfolio (a line_id from list_portfolio_archived_aircraft): then archived is true and you get when and why it left, at what price, the facts it was valued on, and its value history up to that day.

Why one portfolio's value moved, in dollars by driver (market, airframe hours and age, engine time, condition, aircraft record, other inputs), with the aircraft that moved most; and where today's value sits against typical examples of the same aircraft, by the same drivers. Pass window (1d, 7d or 30d; default 1d) for the period the move covers. restated is what a change of valuation model did to earlier values: it is reported beside the move, not in it. Aircraft the period cannot be explained for are counted, never estimated. available is false until a daily valuation has stored explanations.

One portfolio's value by driver (market, airframe hours and age, engine time, condition, aircraft record, other inputs) at every month start of its history, oldest first. Every list has one entry per entry of months. change is why the same aircraft moved since the month before: each driver's amounts are that month's dollars, so add a driver's amounts from one month to another for its effect over that period; change.amount is their sum. level is where the value sits against typical examples of the same make, model and year that month: level.typical plus each driver's amount is level.fleet. The aircraft lists beside them say how many aircraft each figure covers; the rest are counted, never estimated. change.restated is what a restated earlier value did, reported beside the move, not in it. pending_aircraft are left out of level and change while their explanations catch up with new values (normally 0): when it is a large share of the portfolio, say the breakdown is being updated instead of quoting it. Nominal dollars. Use get_portfolio_attribution for the last day, week or month with the aircraft behind it. available is false until a month has been explained.

What happened to the portfolio's aircraft, newest first: value moves, flight activity (dormant, resumed, pattern changes), registration changes and expiries, listings, accidents/incidents, web mentions, and estimated-LTV crossings. Filter with kinds (comma-separated; a prefix ends in '.', e.g. "flight.,listing.") or line_id for one aircraft. Records from before an aircraft was acquired are left out unless include_history is true. Paginate with next_cursor.

Estimated loan balances and estimated LTV per aircraft, the book summary and the watchlist. These are ESTIMATES from each aircraft's purchase price and date under the portfolio's lending assumptions, except where an aircraft has its own loan terms on file (estimate.terms_basis, estimate.line_terms, loan_terms) — those terms win field by field.

One portfolio's fleet value and KPIs, its value history (monthly, same-aircraft index), the split by segment and by state, the value forecast, and the newest events. Pass inflation_base (YYYY-MM) for inflation-adjusted dollars.

The last-known position of each aircraft in the portfolio — live when airborne, else the last ADS-B fix, else its base — with the source of each position.

Fetch one report by id. Use include to inline sub-blocks in a single response, e.g. ["pricing","aircraft","components","inspection","appraiser","client","contents"]. Use only ["print_preflight"] for an owner/admin-only read-only eligibility check returning booleans and an opaque reference, with no report data or token/render/write action.

Mint a short-lived (15 minute) direct download URL for the generated PDF of a report your account can access. Fetch the returned url with a plain GET — it carries its own authority and needs no credentials. Only works once the report has finished generating; poll get_report until report_status is "complete". Before then it returns a 409 whose error carries retry_after_seconds (wait that long before polling again) and, when rendering was rescheduled because every renderer was busy, generation_deferred_until. A 409 with code generation_failed means no PDF will be produced.

Fetch one of a report's structured sub-resources: comparable-sold, market-strength, interpretability, price-timeline, flight-review, flight-history, comparable-aircraft-stats, report-summary, pricing, aircraft, or logbooks. Mirrors the sections of the PDF report.

Historical valuation snapshots for a watchlisted tail (dated value points). Use for value trends, portfolio appreciation/depreciation, and collateral monitoring over time.

Return a stored underwriting enrichment exactly as it was first served, by its enrichment_id — the value, ranges and hull-value check as they stood then, even after a later model release. Visible to the key that created it and to its enterprise workspace.

ML fill-in for missing airframe, engine, and condition fields (SMOH, AFTT, interior/exterior quality, etc.) before a valuation. Identify the aircraft by registration or make_model_id; any fields you supply (including known hours) are preserved and used to estimate the rest. field_sources says which values were provided, taken from the tail's registry/listing data, or imputed. Quality scores use a 1–10 scale on input (a literal 1 reads as like-new, not the worst grade — send 0.1 for the worst) and are RETURNED on the 0–1 scale, where 0.7 means grade 7. Pass the returned values straight to value_aircraft, which accepts either scale.

Extract aircraft specs — AFTT, SMOH (engine 1, and engine 2 for twins), prop time, year, and interior/exterior quality (1–10), plus avionics mentioned — from observable page content: visible text and/or image URLs (a listing's own photos, or data: URLs). Uses the vision/LLM "autopilot inference" behind on-site valuation pre-fill. Anchor with registration or make_model_id to pull make/model + year from the FAA registry; set impute=true to fill gaps with the imputation model. Returns specs, per-field sources, and a ready-to-POST report_input for create_valuation_report. Requires Windsock PRO or Enterprise.

List the pre-buy diligence checklist items for a report. Each item carries its category, title, guidance, critical flag, current state (pending/pass/flag/fail/na), source (ad/stc/logbook/rag/user), dollar value-impact band, AD/STC ref ids, and any evidence (notes, cited logbook page ids, photos).

Aircraft segment keys (e.g. single_engine_piston) used to scope market metrics. Pass a key as the category argument to get_market_metric.

Catalog of macro GA market metrics Windsock tracks (stable identifiers, labels, units, and whether each supports forecasting). Discover valid metric names before calling get_market_metric.

The aircraft in one portfolio: tail, make/model/year, latest value and change, tracking status (last seen, flight activity, listing, registration) and the estimated loan balance. Each row's line_id addresses that aircraft in the other portfolio tools. A row's imputed_fields names the facts Windsock filled in (estimated, or from the FAA registry) rather than the holder provided, and unknown_fields the ones the holder cleared or gave unreadably; every other fact is the holder's own. Paginate with next_cursor (default 50 per page).

The aircraft that have left one portfolio (sold, paid off, listing ended…), newest exit first, with totals: when each came in and at what price, when and why it left and at what price, and Windsock's last value before it left. On a portfolio of aircraft for sale the entry price is the first asking price and the exit price the last. Each row's line_id addresses that aircraft in get_portfolio_aircraft (its full history) and update_portfolio_aircraft.

The portfolio's locked point-in-time reports, newest first: name, kind, as-of date, status and aircraft counts.

Your Pro Portfolios (your own and your team's), with fleet value, aircraft count and when each was last revalued. Start here: every other portfolio tool takes a portfolio_id from this list — never guess one.

Saved Stress Lab scenarios for the portfolio (market shocks and their inputs), newest first.

List the tails on your watchlist with their latest tracking state.

Canonical registry + distilled aircraft profile for a registration. Accepts a US N-number OR an international mark (C-GKUH, VH-ABC, PH-XYZ, 9V-BLL — 17 registers). Returns structured aircraft data plus make_model_id and avionics_ids — the IDs needed downstream for valuation and reference lookups. The first step in any "value this tail" workflow. For a non-US aircraft the response carries a registration_authority block naming the state of registry, and the faa_ads / faa_stcs lists carry a jurisdiction note: those documents are FAA-issued and apply to the TYPE, not to that registration — the aircraft's own authority issues its directives.

Registry-wide aircraft search — the fleet / market-research search surface. Returns individual registered tails matching an AND-combined filter set (make/model, US state, city, year, tail number, current registrant name, or geographic radius), with pagination and sorting. Resolve each model name to a make_model_id with search_make_models first; to cover several models in one search pass them as a list with condition "in". For population totals (e.g. "how many R182s in Oregon") prefer count_aircraft, which avoids paging. Each filter is {field_name, condition, value}.

Search FAA Airworthiness Directive records, optionally filtered by make_model_id and compliance status. For pre-buy AD review, maintenance planning, and appraisal compliance sections.

Search avionics equipment names/types, returning avionics_ids that affect equipment-adjusted valuations. Use to map panel/upgrade text to canonical ids.

Semantic/hybrid search over digitized aircraft logbook entries across reports you can access. Each hit includes date, summary, OCR text, extracted fields, and page ids for citation. Scope to a report with report_id.

Text search over FAA make/model names, returning make_model_id values needed by value_aircraft, impute_aircraft_specs, and reference lookups. Use to resolve "2015 Cirrus SR22" to a canonical id when no tail number is available.

Paginated search over appraisal/valuation reports your account can access. Filter by registration, year, make_model_id, price bounds, and whether logbooks are attached.

Search STC records, optionally filtered by make_model_id — certificate numbers, descriptions, applicability. For pre-buy due diligence and documenting mods that affect value. STC applicability lists can run to hundreds of models, making a single row ~90K+ characters; pass slim=true to drop the large applicability strings (model_series, tc_number, tc_holder) in favor of an applicability_summary with counts, so the endpoint stays usable at realistic limits.

Describe the aircraft (and owners) you want in plain words, e.g. "Cirrus SR22s in Texas bought in the last two years" or "twin pistons near Denver with an autopilot that haven't flown in a year", and get back search filters (make/model, type, place, year, avionics, flying, ownership, accidents, market balance and more) with a one-line reading of the request and anything that couldn't be expressed. Set execute=true to also get the matching aircraft. To page or re-run, send the returned filters back without a prompt (no new model call). The filters use a wider vocabulary than search_aircraft, so run them here. One call per second.

PRO FILTERS (marked pro: true; need Windsock Pro or a paid API plan to run): avionics (avionics_categories, standardized_avionic_ids), owner profile (pilot_type, pilot_level, med_class, end_of_career_pilot), ownership timing (current_owner_start_date, inferred_sale_date: estimated from the first new-owner FAA registration date minus the 30-day median processing lag, not a verified closing date; num_unique_faa_registrants, avg_owner_hold_years: average years each owner on record has kept it), registration status (registration_pending, up_for_renewal_soon, expiration_date), flying activity (last_airborne_at, flight_hours_last_year, adsb_signal_strength, and last_seen_state / last_seen_near: where ADS-B last saw it, as opposed to state / location_point, where it lives; utilization_vs_peers: low, typical or high days flown in the last year against similar aircraft; utilization_trend: down for a lasting recent drop against its own usual flying, or steady), market_balance, and the score levels sale_likelihood (how likely to sell in the next few months) and dealflow (how quickly it would sell at its value) — each is high, medium or low, thirds of US aircraft — and estimated_value (Windsock's weekly preliminary value in US dollars; gt, gte, lt or lte). Without Pro, the answer still shows them but lists them under locked with an upgrade link and does not run the search: tell the user which filters need Pro, or drop them and re-run with the rest.

Add a tail to your portfolio watchlist for recurring valuation snapshots and change monitoring. Requires make_model_id and aircraft_info.year; registration identifies the tail.

Update one diligence item: set its state (pending/pass/flag/fail/na), add notes or photo keys, set the value_impact band, or edit a user item's fields. Use this to tick items off as you verify them.

Change what is on file about one aircraft in a portfolio you own, whether it is still in the portfolio or has left it. Send only what changes. On an aircraft still in the portfolio, facts the valuation depends on (tail, year, hours, engine times, condition, location, the date it came in) re-price its history, which takes a minute or two (repricing is true in the reply). On one that has left, every change is recorded, and one that would have moved its value history (those facts, or an exit moved later) has that history priced again in place, up to the day it left: the reply says repricing and value_history_stale, and list_portfolio_archived_aircraft shows value_history_stale false once the new values are in (a minute or two). The entry price, asking price, notes and the exit facts (why it left, when, for how much) never affect values. Exit facts apply only to an aircraft that has left. This does not change an aircraft's make and model, and does not add, archive, restore or delete aircraft. Confirm the change with the user before calling.

Machine-generated aircraft market value at a single point in time, from today back to 1960. Provide a tail number OR a full spec (make_model_id + aircraft_info). Optional as_of_date selects the contemporary model (>= 2020-01-01 or omitted) or the deep-history longitudinal model (before 2020). Set include=["explanation"] or ["uncertainty"] for richer output. The flagship valuation tool.