…

Product contract

Customers speak the official OpenAI Responses document. The dest peel is https://api.sylphx.ai/v1 with Authorization: Bearer sk-sx-…. That envelope is an AI product key. It is not Binding. This site does not invent a second schema.

Download Product Contract (OpenAPI)

Machine-readable contract: /contract/ai.product.openapi.json, the same bytes as contract/ai.product.openapi.json. First success is curl against the peel, not an npm install.

What you send

  • POST https://api.sylphx.ai/v1/responses — create, including stream: true
  • Retrieve, delete, compact, and cancel stored responses on the same peel when the official contract permits it
  • GET https://api.sylphx.ai/v1/models under the same key — admitted SKUs, our SELL prices, no residual dump
  • Messages (POST https://api.sylphx.ai/v1/messages) is a second encoding that normalizes once into the Responses document

What this is not

  • Not Binding, and not a reason to send Binding to the AI peel.
  • Not a public Chat Completions facade. POST https://api.sylphx.ai/v1/chat/completions is retired.
  • Not a third conversation protocol on this site.
  • Not marketing HTML on the peel host. The peel is the API door.
  • Not dens Console. Account pages on this site are projections so you can mint keys.

Honesty on the wire

  • Changing model does not change the official document. Each request names one concrete admitted SKU; the cancelled auto router is not an alias.
  • Unknown fields and duplicate keys fail closed. The product does not guess intent.
  • Hosted web_search and tool_search are model-initiated. Listing them is not execution.
  • SELL prices are ours. Residual COGS never becomes a customer routing API.

Normative field list: docs/protocol.md. First success · Docs · Pricing.