Skip to content

Reference ​

Lookup material: endpoints, SDK surface, contract addresses, chain and provider tables, environment variables, and the failure modes each produces.

HTTP API ​

Two mounts on bz-backend:

MountContentsRoute files
/apiThe original surface — trading, providers, fiat, perps, DCA, Autopilot, plus the whole ecosystem layer65
/api/v1BlazAI, dApp builder, audit, safety, wallet cards, training data, feedback, notifications9
/api/pinataIPFS pinning1

Base URLs: https://api.blazpay.com/api in production, http://localhost:5000/api locally.

PageCovers
Trading & quotesSSE quotes, transaction build, signing, history
Provider proxiesThe 14 key-bearing provider passthroughs
Fiat on/off-ramp5 ramps, catalogues, webhooks
Perpetuals (Orderly)Account lifecycle, orders, positions
DCACSIP positions, fills, claims
AutopilotAgents, policies, activity
BlazAI chatStreaming chat, sessions, suggestions
Audit & safetyReports, certificates, token scans, wallet cards
dApp builderProjects, versions, smart accounts
Platform & ecosystemThe remaining 50-odd route groups

SDK & contracts ​

PageCovers
swap-sdkTradeManager, AggregatorFactory, RelayerFactory, Quote, constants
Contract addressesEvery deployed proxy and implementation
Contract ABIsWhere each ABI lives and how they stay in sync

Data tables ​

PageCovers
Chains36 named, 22 settleable, 24 with landing pages
Liquidity providers26 integrated, 21 registered
Environment variablesEvery variable, grouped, secrets marked
Errors & failure modesSymptom → cause → fix

Conventions ​

Read conventions before using the API pages — it covers response envelopes, the wallet-parameter pattern, SSE framing, address casing and pagination.

The API is internal-first

There is no published public API, no versioned deprecation policy and no API keys for third parties. /api/v1 is a code-organisation boundary, not a compatibility contract. Endpoints change without notice, and several are administrative (catalogue refresh, seeders) rather than product surfaces.

Treat everything here as documentation of the current implementation, not as a stable interface.

Internal + developer documentation. Usage figures are point-in-time snapshots — re-verify before publishing them.