find_plans
Pricing plans across the catalog. An API's pricing tiers. meta says who wrote the file (method), when it was read (provenance_date), who the page prices for (audience), how (pricing_basis), and whether a price is stale. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Free text over name + description, e.g. "sms". | |
| page | No | Page number, 1-based (default 1). | |
| sort | No | Order: relevance / provider / name, or plan_count (largest first). | |
| tags | No | Tag slugs, e.g. ["payments"]. On providers: what the company does (see api_tags). | |
| limit | No | Results per page, 1-100 (default 25). | |
| match | No | How `tags` combine: any (default) or all. | any |
| method | No | Who wrote the file: "searched" (transcribed from the provider's page), "probed" (read live), "generated" (API Evangelist sweep, unverified), "unmarked". | |
| context | No | Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong. | |
| include | No | Pass ["content"] to inline each artifact's body instead of just its URL. | |
| audience | No | Who the pricing page prices for: "developer-api" (API or platform usage), "business-product" (the product the API comes with), "consumer" (a fee schedule), "unclear". | |
| providers | No | Provider slugs, e.g. ["stripe"]. | |
| pricing_basis | No | How it is priced: "per-call", "per-seat", "ad-valorem", "flat-platform", "tiered-subscription", "usage-other", "negotiated", "free", "none". |