Flynnstone Developers

No API key is required. No separate sandbox is required. The production API is safe for read-only integration testing because it cannot create, change, or expose private records. Start with API discovery or load the Flynnstone OpenAPI 3.1 contract.

Quickstart

curl --fail-with-body \
  'https://flynnstone.ai/api/v1/articles?limit=10'

curl --fail-with-body \
  'https://flynnstone.ai/api/v1/articles/butchery-roll-up-thesis'

Endpoint reference

• GET /api/v1 — version, policy, and route discovery.
• GET /api/v1/articles — indexed article catalog.
• GET /api/v1/articles/{slug} — one indexed article.
• GET /api/v1/index/latest — latest indexed series issue.
• GET /api/v1/sources — approved public source catalog.

The article catalog accepts topic, article_type, published_after, cursor, and limit. Limit must be 1–50. Cursors are opaque and valid only with the filters that produced them.

Responses and errors

Successful reads return application/json. Every 4xx or 5xx returns RFC 9457 application/problem+json with type, title, status, detail, instance, a stable code, and an actionable resolution.

{
  "type": "https://flynnstone.ai/developers#problem-article_not_found",
  "title": "Article not found",
  "status": 404,
  "detail": "No indexed Flynnstone article has this slug.",
  "instance": "/api/v1/articles/example",
  "code": "article_not_found",
  "resolution": "Review the developer quickstart and OpenAPI contract, then correct the request."
}

Limits and caching

Each REST response uses the IETF HTTPAPI draft-11 fields RateLimit-Policy: "public";q=30;w=60 and RateLimit: "public";r=29;t=60. A 429 also sends a positive Retry-After. The limit applies per public route and client address.

Read responses send Cache-Control, a strong ETag, and Last-Modified. Send If-None-Match or If-Modified-Since to receive 304 when the representation is unchanged.

Versioning, deprecation, and sunset

The major version stays in the URL. Flynnstone can add optional fields and new routes to v1. Removing fields, changing their meaning or type, or adding a required input needs a parallel v2 route.

No v1 route is deprecated. A future notice will appear here first with its replacement and migration steps. A deprecated route will send RFC 9745 Deprecation: @unix-seconds and a rel="deprecation" link. When retirement is scheduled, it will also send an RFC 8594 Sunset HTTP-date. Flynnstone will keep both major versions available for at least 180 days after the first public notice. A dated security or legal incident is the only exception to that notice period.

Other Flynnstone formats

Read the Flynnstone agent access guide, Flynnstone RSS feed, or Flynnstone JSON Feed. The future read-only MCP endpoint is https://mcp.flynnstone.ai/mcp. It remains inactive until its separate Phase 4 gates pass.