Your first connection.

Connect over MCP

Public discovery endpoint: https://ai.agentik.cc/mcp/public. It exposes discover_tools and inspect_tool.

Authenticated endpoint: https://ai.agentik.cc/mcp. Use the client’s supported OAuth flow or an Agentik API key. Authorised clients can also call run_tool and get_run. Use get_account for the actual workspace balance and payment status. prepare_topup prepares a human review link for a requested credit amount; it does not charge a card. Wait for settled credit before resuming an authorised paid task. Follow the client setup guides.

Try discovery over REST

This request only searches the catalog; it does not call a provider.

curl -sS 'https://api.agentik.cc/v1/discover' \
  -H 'Content-Type: application/json' \
  --data '{"query":"search the web","limit":3}'

Choose an exact tool_id from the result. Read its schema, availability and pricing with GET /v1/tools/{provider}/{tool}. Do not invent an ID or inputs.

Before execution

Start through sign up. The guided setup prepares your workspace automatically and preserves your chosen app. Authorise its connection with your account; developers can also create a key in workspace settings. You can skip setup and resume its steps from the dashboard. Keep credentials out of prompts, source code, screenshots and URLs. Review the tool’s price and side effects with the person who requested the task.

For REST, POST https://api.agentik.cc/v1/run takes {"tool_id":"<selected tool>","input":{...}}. Send Authorization: Bearer <your key> and a fresh Idempotency-Key for this intended execution. The placeholders are not runnable input.

Read the returned state. Reuse the same idempotency key for a transport retry; poll the existing run when it is pending. See idempotency and asynchronous executions.