VeTrade

Developer docs

Auth

Current access policy and future authentication posture for the public beta.

Read articleBrowse docs

The checked-in public beta handlers do not require an API key or bearer token for HTTP plans and reads. Hosted infrastructure can still impose limits or change access.

Last technical review: 23 October 2026, against the repository handlers and MCP implementation. This is a source review, not a live access test or future-access guarantee.

Current endpoint coverage

  • GET and POST /v2/swap-plans
  • GET and POST /v2/transfer-plans
  • GET and POST /v2/limit-order-plans
  • GET /v2/limit-orders and GET /v2/limit-orders/{orderId}
  • Hosted MCP at https://mcp.vetrade.vet

No signer key belongs in an auth header or hosted tool argument. Local execution credentials are separate from public API access.

Runnable HTTP request

Prerequisite: curl. This read-only request needs no downloaded request file or auth header:

curl -fsS https://vetrade.vet/v2/swap-plans

Expected: JSON endpoint guidance, including supportedMethods and a POST example. To request a quote, use the complete inline JSON request.

MCP configuration

[mcp_servers.vetrade_ai]
url = "https://mcp.vetrade.vet"

Start a fresh client process after changing its configuration. Continue with the first read-only MCP call.

If access fails

For 401 or 403, check the actual response and current published access policy; do not guess credentials or send wallet secrets. For rate limiting, respect the server retry guidance. For API validation failures, use Errors. Future API-key or tier changes are not a promise of current behavior.