Live pricing
Check input, output, and capability pricing before larger usage.
TackleKey
Dify integration
Use TackleKey as an OpenAI-compatible provider in Dify
Dify-style applications often need a stable custom provider: base URL, API key, model name, and logs that explain failed requests before a workflow grows.
Minimal configuration example
Provider type: OpenAI-compatible
Base URL: https://api.tacklekey.com/v1
API Key: tk-project-key
Model: openai/gpt-4o-mini
First test prompt:
Return one health-check sentence.Configuration checklist
| Item | How to verify |
|---|---|
| Provider type | Choose an OpenAI-compatible or custom OpenAI provider option. |
| Base URL | Use the API endpoint base URL, not the TackleKey console URL. |
| Key scope | Use a dedicated project key for Dify so spend can be isolated. |
| Workflow test | Run one tiny prompt, then inspect logs before enabling production workflows. |
Next steps
Examples hub
Copy cURL, Node.js, Python, or client configuration examples.
Troubleshooting
Debug 401, 429, invalid model, base URL, and billing issues.
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.