API Guide

Integrate FluxA via HTTP / curl

The HTTP API is the lowest-level way to integrate FluxA. Instead of going through an MCP client or the CLI, your backend or agent runtime talks directly to two services:

Service	Base URL	Used for
Agent ID	https://agentid.fluxapay.xyz	Register an agent, refresh its JWT, issue/verify Verifiable Credentials
Wallet API	https://walletapi.fluxapay.xyz	Payments, mandates, payouts, payment links, refunds

Authenticate wallet calls with Authorization: Bearer <agent-jwt> (the login JWT from registration — not a VC). Most wallet APIs also need the agent to be linked to a user's FluxA Wallet; the first call that needs it returns an authorizationUrl for the user.

You'll also find high-level examples at Dashboard → Integration → API Guide tab.

Outline:

• Agent registration — obtain agent_id, token, and jwt; refresh the JWT.
• Verifiable Credentials (VC) — identity tokens for third-party login, and the JWKS used to verify them.
• Agent status — one call for balances, monthly headroom, mandates, and recent transactions.
• X402 payments (V1) — pay a 402 bill, with user approval when required.
• X402 V3 payments — pay from a signed mandate without per-payment approval (also covers x402 v2 requirements).
• Mandates — create and query pre-authorized spending budgets.
• Payouts — send USDC out of the wallet and track the outcome.
• Payment links — create shareable links to receive payments; the public /paymentlink/:id x402 endpoint.
• Received payments and Refunds — reconcile and refund incoming payments.
• Unify Payment Link (UPL) — pay any agent by its Agent ID.
• Linked cards (Beta) — read-only view of linked cards and card mandates.
• Error codes and Units & networks.

The complete machine-readable reference is in the API Reference and openapi.json.