findasaas API and developer docs
The whole directory is readable programmatically. Read endpoints need no key, no signup and no rate-limit registration — so an agent can start with a single request.
Quick start
Search the directory without any credential:
curl "https://findasaas.com/api/v1/listings?search=invoicing&per_page=5"
The full contract lives at /openapi.json as an OpenAPI 3.1 document. Every operation has a unique operationId, a description and typed response schemas, so it converts directly into LLM function-calling tools or a generated client.
Endpoints
GET /api/v1/listings — search and filter. Query params: search, category, page, per_page (max 100).
GET /api/v1/listings/{slug} — one listing, including its official website and category tags.
GET /api/v1/categories — the category vocabulary. Call this before filtering by category rather than guessing slugs; an unknown slug returns 404 instead of silently returning everything.
Errors
Failures are JSON, never an HTML page, including unknown paths (404) and wrong methods (405, with an Allow header). Branch on code, which is stable — the message is for humans and may be reworded.
{
"error": {
"code": "not_found",
"message": "Unknown category: crm-tools",
"hint": "Call GET /api/v1/categories for the list of valid category slugs.",
"documentation": "https://findasaas.com/developers"
}
}Rate limits
Every /api/v1 response says where you stand, using the IETF RateLimit header fields (draft-ietf-httpapi-ratelimit-headers). The limit is 60 requests per 60 seconds per client IP.
RateLimit-Policy: "default";q=60;w=60 RateLimit: "default";r=57;t=42
q is the quota, w the window in seconds, r the requests you have left, and t the seconds until the window resets. Over the limit you get a 429 with the standard JSON error (rate_limited) and a Retry-After header in seconds. Browsers can read all of these headers: they are listed in Access-Control-Expose-Headers.
The limiter is best-effort: counters live in memory on each edge instance, so a client spread across many locations can get more than the quota in total, but never less than the headers promise.
Versioning and deprecation policy
The version is in the path. v1 is stable: we add fields and endpoints to it, but a breaking change (removing or renaming a field, changing a type or meaning, removing an endpoint) only ships as a new version such as /api/v2, never inside v1.
When an endpoint is going away, it is first marked deprecated. From then on its responses carry three headers, and the sunset date is at least 6 months after the deprecation date:
Deprecation: @1798761600 Sunset: Thu, 01 Jul 2027 00:00:00 GMT Link: <https://findasaas.com/developers#versioning>; rel="deprecation"; type="text/html" Link: <https://findasaas.com/api/v2/listings>; rel="successor-version"
Deprecation (RFC 9745) is the date it was deprecated, as a Unix timestamp, Sunset (RFC 8594) is when it stops working, and the deprecation link points here. A successor-version link names the replacement when there is one. Endpoints that are not deprecated send none of these headers, so their presence is the signal. Nothing is deprecated today.
Markdown instead of HTML
Every public page serves a markdown representation through content negotiation, so you do not have to scrape the rendered app. Responses set Vary: Accept.
curl -H "Accept: text/markdown" https://findasaas.com/
API keys and scopes
Write access uses a personal key, generated self-serve from your dashboard — there is no sales step and no approval queue. Send it as a bearer token, and grant only the scopes the integration needs:
curl -H "Authorization: Bearer fas_..." https://findasaas.com/api/v1/listings
listings:read— Read public directory listings and categories.listings:write— Create and update listings you own.posts:read— Read product updates on listings you own.posts:write— Publish and edit product updates on listings you own.checkout:write— Create and complete agentic commerce checkouts (ACP and UCP) that buy Featured or a custom page for a listing.
A call outside a key's scopes returns 403 with the scope it needed named in requiredScopes, so an agent can tell the difference between "wrong credential" and "insufficient grant" without guessing.
findasaas MCP server
There are two MCP servers, both Streamable HTTP, listed in the manifest at /.well-known/mcp.json. The public server at https://findasaas.com/api/mcp/public needs no credentials and exposes read-only directory tools: search_listings, get_listing and list_categories.
The authenticated server at https://findasaas.com/api/mcp exposes a founder's own listings as tools: read them, design the custom detail page, and publish product updates.
The authenticated server uses OAuth 2.1 with PKCE — discovery at /.well-known/oauth-authorization-server — or the same personal API key, for clients that cannot do OAuth. Directory search also works over the REST endpoints above.
Free to use
Reading the directory is free and unauthenticated. Listing a product is free. The paid features are one-time charges for boosts and the custom detail page — there is no subscription and nothing to talk to a salesperson about. See pricing.
Machine-readable index
/llms.txt states when an agent should reach for this site and when it should not. /openapi.json is the contract, /.well-known/mcp.json the MCP manifest, and /sitemap.xml every indexable URL.