Skip to main content
Eight official clients. Each one is generated from the same curated OpenAPI contract that backs this reference, so the request and response types in your editor are the server’s types — not a hand-maintained mirror that drifts. Because they are generated from that contract, the clients expose exactly the published surface and nothing more: a method appears when its route becomes public, not before. Every client defaults to https://api.rafflesia.ai, reads RAFFLESIA_API_KEY from the environment when no key is passed, and groups operations by resource (client.homology.…).

Install and construct

Requirements

What the SDKs give you beyond HTTP

  • Typed envelopes. ok, data, warnings, evidence, and provenance are typed, so warnings is hard to ignore by accident.
  • Typed errors. Failures raise a client error carrying status_code, type, code, param, doc_url, details, and the request_id.
  • Pagination helpers. Cursor iteration for the list endpoints.
  • A base URL you can point anywhere. Every client accepts a base URL for local engines and staging.
Sources live at github.com/rafflesia-ai.