Tradeics APIs authenticate callers with a bearer token issued for your workspace. Keys and sessions resolve to one workspace (users can belong to many). The same family of credentials unlocks REST V2, MCP Servers, and (with LLM keys) inference.

Current model

Send the token on every request:

Authorization: Bearer <your_api_key>
Content-Type: application/json

Until Tradeics Platform ships self-serve key management:

1. Create a Tradeics account at tradeics.example/get-started.
2. Contact support (or your account manager) for early API access — ask for MCP enablement if agents will connect.
3. Store the key only in your secrets manager — never in client-side code, public repos, or pasted into shared chat logs.

Practices to follow now

• Prefer server-to-server calls. Do not embed keys in mobile or browser apps.
• Rotate keys when people leave the project or when a leak is suspected.
• Scope integrations by environment when you receive separate staging credentials (versioning).
• Log request IDs / correlation IDs from responses when debugging with support.
• For MCP hosts that cannot send headers, use a short-lived token via ?token= only as a fallback.

Next

• First requestAuthenticate and call an endpoint.Read
• MCP ServersConnect Docs / Platform / AI MCP.Read
• Agent SkillsTeach agents Tradeics conventions.Read
• REST API V2Full route contracts.Read
• Call the LLMInference auth and SDKs.Read