API Keys

Manage API keys for your integrations. Read the key lifecycle guide →

Your Keys

Copy Key ID copies the internal key identifier, not the secret API key. Secret keys are only shown once when created or rotated.

Loading…

How to use this key

Copy the secret immediately into a local secret store or environment variable. The secret is shown once only. Keep scopes tight and use devnet for execution tests.

API Base URL

https://api.trucore.xyz

MCP Endpoint

https://api.trucore.xyz/mcp/v1

Auth Header

X-API-Key

Env Var

ATF_API_KEY

Canonical secret path

~/.openclaw/secrets/atf.env

Place your secret in this file and load with: source ~/.openclaw/secrets/atf.env

Recommended minimum scopes

API / CLI test

atf:probeatf:simulateatf:verifyatf:explain

MCP test

atf:probeatf:simulateatf:verifyatf:explainatf:mcp

Copy-ready snippets

Env file (~/.openclaw/secrets/atf.env)

# ATF customer API key
export ATF_API_KEY=<your-secret-key>
export ATF_BASE_URL=https://api.trucore.xyz
export ATF_MCP_ENDPOINT=https://api.trucore.xyz/mcp/v1

curl - probe a swap intent

curl -sS https://api.trucore.xyz/v1/intents \
  -H "X-API-Key: $ATF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"intent_type":"swap","input_mint":"So111...","output_mint":"EPjFW...","amount":1000000,"slippage_bps":50}'

MCP - JSON-RPC call

curl -sS https://api.trucore.xyz/mcp/v1 \
  -H "X-API-Key: $ATF_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"probe_transaction","arguments":{"intent_type":"swap","input_mint":"So111...","output_mint":"EPjFW...","amount":1000000,"slippage_bps":50}}}'

Self-verification steps

1. API check

POST /v1/receipts/verify with your key. HTTP 200 with valid:false, reason:signature_invalid means auth succeeded and reached protected logic.

2. MCP check

POST to MCP endpoint with tools/call method, tool explain_decision, argument decision_source: "verify". Response should contain isError:false.

3. CLI check

Run source ~/.openclaw/secrets/atf.env && atf --help. If prevented by an OS execution policy, that is environment friction, not an ATF failure.

Plan: free.

Revoke permanently deactivates a key. Revoked keys cannot be restored. Rotate revokes the old key and creates a replacement - existing integrations using the old key will immediately stop working.