Skip to main content

Base URL

Authentication

All endpoints except health check and internal cluster endpoints require a JWT Bearer token:
Contact support for API access credentials.

Endpoints


POST /api/v1/execute-intent

Execute an on-chain swap, register a conditional rule, or close a position.

Request

Response

Execution status values


POST /api/v1/normalize-intent

Parse and enrich an intent XML with resolved token addresses and USD values. Use this to preview what TIM will execute before submitting.

Request

Response

The response intent field contains the normalized intent as a JSON string with resolved addresses and computed values.

POST /api/v1/trades/simulate

Simulate a trade to check token liquidity and price impact without executing.

Request

Response (success)

Response (failure)

Simulation error codes


GET /api/v1/tokens/resolve

Resolve a token symbol to contract addresses across chains.

Query parameters

Response


GET /api/v1/transactions

List transaction history for the authenticated user.

Query parameters


Error format

All errors follow this structure:

Common error codes

MCP Hub alternative

MCP Hub wraps TIM with the same capabilities via MCP tool calling. If you are building an AI agent that supports MCP, you can use genalpha_tim_execute_intent through the MCP Hub API instead of calling the HTTP API directly. Both accept the same intent format and return equivalent responses.