Core API paths
Models, Chat Completions, Responses, Embeddings, Image Generation, Speech, Transcriptions, and Moderations.
TackleKey
Developer integration kit
Import TackleKey into Postman or an OpenAPI client
Use the public TackleKey core API description to inspect request schemas, generate a client, or import eight safe starter requests without putting a real API key in a shared file.
What is included
Safe variables
The collection contains placeholders for the base URL, project key, and model IDs. It contains no production credentials.
Current source
The public OpenAPI file is derived from the project's relay specification and branded for the TackleKey production endpoint.
Postman setup
| Step | Action |
|---|---|
| 1 | Import https://tacklekey.com/tacklekey.postman_collection.json into Postman. |
| 2 | Set the collection variable api_key to a project key created in your TackleKey console. |
| 3 | Choose model variables from the live pricing page; placeholder model names may not be enabled for every account. |
| 4 | Run List models, then send one small Chat or Responses request and check logs and balance records. |
OpenAPI use
Tools that support OpenAPI 3 can read https://tacklekey.com/openapi.json. The public file intentionally focuses on eight core endpoints instead of every provider-specific relay route. Bearer authentication is declared globally.
Never commit an exported Postman environment containing a real project key. The public collection uses
replace-with-project-key and model placeholders by design.FAQ
Does the Postman file contain a TackleKey API key?
No. It contains only a safe placeholder. Add your own project key locally after importing the collection.
Are all placeholder models guaranteed to be available?
No. Check the live pricing page and your project permissions before sending a request.
Can I generate a client from the OpenAPI file?
Yes, with an OpenAPI 3 compatible generator. Review the generated client and test one small request before production use.
Try TackleKey with one OpenAI-compatible change
Create an account, generate a project API key, then replace your client base URL with the TackleKey endpoint. Keep keys server-side and verify live pricing before scaling traffic.