Payments & swaps
for Concordium agents.
Concordex gives agents, SaaS backends and treasury automation a clean way to send and swap Protocol-Level Tokens on Concordium. Pay in any PLT, receive in any PLT. Vault-held keys, identity-aware, policy-bound, audited on-chain — the payment & DEX layer the agentic stack needs. Designed for the Concordium agent registry — verifiable agents linked to real identities — landing in stage 2. Stake CCDX to earn 10 bps on every swap.
One wallet. Three ways to call it.
A hardened vault holds your project's keys. Your code, your agent, and the humans on your team each reach the same wallet through the surface that fits them.
Vault custody
Project keys live inside a Shamir-sealed OpenBao vault. Concordex itself can't unilaterally spend — every payment is authenticated against a project credential bound by your policy.
Payments & swaps API
One HTTPS call from your backend. POST /v1/payments sends a PLT. POST /v1/swaps swaps across PLTs. Pay in any PLT, receive in any PLT — atomic, idempotent, webhook-acknowledged.
Hosted MCP App
A managed MCP endpoint that exposes pay, swap, quote and get_balances as native tools. Drop it into Claude, Cursor, or any MCP client.
Web UI for humans
See every payment your agent made, who signed it, current balances, pending dual-control approvals. Edit policy, rotate keys, hit the kill switch — without a deploy.
Audit & scope
Every payment is on-chain, identity-bound and inside a per-project spend policy. Per-key rate limits, daily caps, allow-lists, optional approval thresholds — revoke a key instantly.
Built on Concordium PLTs
PLTs live on user accounts, not contracts. The protocol itself enforces who can move them — the first chain asset that's actually safe to expose behind a public API.
From agent decision to on-chain finality, in four moves.
Same flow for payments and swaps. No new wallet for your users. No new SDK on every microservice. Just one signed call to the vault.
Register your project
Sign up, bring a Concordium account (or run the standard identity flow first), upload keys to the vault, set spend policy, mint scoped API keys.
Hit the API
Your code (or agent's tool call) posts a payment or a swap — amount, token, recipient, idempotency key. JSON in, JSON out.
Vault signs, chain settles
Concordex validates against policy, asks the vault to sign, submits. Settlement is on-chain in seconds.
Webhook + dashboard
Webhook on submitted, finalised, rejected. Dashboard shows tx hash, signer, audit trail.
One primitive. Many patterns. Counting.
The same secure-vault + clean-API combo shows up in very different shapes depending on who's calling it.
AI agents paying for tools
Your LLM-driven agent calls paid APIs — data, inference, search, voice — and pays per call in PLT. Scoped key, tight policy, no treasury exposure.
# MCP tool call inside Claude / Cursor
agent.pay(to="openai_api",
amount="0.02", token="EURX") SaaS billing & payouts
Run subscriptions, usage-based billing or marketplace payouts in PLT. Keep your billing logic; we handle signing, finality, audit.
POST /v1/payments
{ "to": "acct_creator_8331",
"amount": "42.00",
"token": "EURX" } Treasury automation
Scheduled outgoing payments, rules-based sweeps, supplier disbursements. Dual-control approvals over threshold; clean audit for finance.
# policy.yaml
daily_cap: 50_000
approval_above: 5_000
allow: ["vendor_*"] Agent-to-agent settlement
Two autonomous services clearing on every call — quote-for-fill, signal-for-execution. Bundled payment + delivery proof makes each leg atomic.
pay_on_proof(
to="agent_b",
amount="0.10",
proof="signed_response_hash") Programmatic disbursements
Affiliate payouts, grants, content royalties, referral rebates. Idempotency keys make replays safe; webhooks close the loop with your records.
batch.create(items=[
{"to":"u_1", "amount":"3.50"},
{"to":"u_2", "amount":"7.10"},
]) Operator wallets for fleets
Devices, nodes or agents sending small PLT payments in the field. Each operator gets a scoped key under one parent project. Revoke one, fleet runs on.
keys.issue(parent="fleet_eu",
scope="node_4421",
cap="5/day") Pay across PLTs
Hold one PLT, recipient wants another. One signed call quotes the matching pool, executes the swap, settles atomic on chain. Today the orchestrator routes via the Concordex treasury; PLT-locks take over once shipped. No two-leg dance for the caller.
POST /v1/payments
{ "pay_with": "CCDX",
"to": "agent_b",
"amount": "42.00",
"token": "EURX" } Treasury swap & rebalance
Quote first, swap after, all under your project's spend policy. Slippage caps, allowed-pair lists and dual-control approvals apply to swaps the same way they apply to payments. Pairs are PLT↔CCD; cross-PLT trades route through CCD.
POST /v1/swaps
{ "from": "EURX",
"to": "CCDX",
"amount_in": "5000",
"max_slippage": "0.30%" } Earn fees as a liquidity provider
Hold a meaningful PLT bag (stablecoin, asset-backed, platform-token)? Delegate scoped, capped liquidity through a PLT lock and earn the LP fee — paid in the same PLT — on every swap routed through it. Funds never leave your PL-account; lock parameters bound every outflow.
POST /v1/locks
{ "token": "EURX",
"max_outflow": "100000",
"per_swap_cap": "5000",
"fee_bps": 25,
"expires_in": "72h" } Keys never leave the box. Including from us.
Concordex runs a hardened HashiCorp-compatible vault (OpenBao) inside a private network. The vault stores wallet keys, signs every payment and swap on the Concordium chain, and exposes nothing to the public internet.
Shamir-sealed
Vault unseal requires a 3-of-5 quorum of operator shares. Even Concordex operators cannot unseal alone. Recovery shares held offline.
Per-project scoping
Each project gets its own wallet, policy and API keys covering both payments and swaps. No shared keyring. A blast-radius exploit on one project never touches any other.
Append-only audit
Every sign, payment, swap, key issue and policy change is recorded. Pull your project's audit log via the API; we keep an internal one too.
Fees in. CCDX rewards out.
Every payment and every swap routed through Concordex generates a fee. Liquidity providers earn the swap fee directly, in the PLT they delegated. On top of that, a small protocol fee (10 bps) flows back to CCDX stakers, a lock wallet, and the protocol treasury. Higher API volume — payments or swaps — = higher LP earnings and higher CCDX rewards. Usage, liquidity, and value alignment, on-chain.
Who earns what, per swap
Each swap charges two stacked fees. The LP fee (10–50 bps, LP-set within bounds) goes directly to the liquidity provider whose lock got used, paid in the PLT or CCD being moved. The protocol fee (10 bps) goes to CCDX, split 45/45/10 below. Concordex itself does not provide liquidity — third-party LPs (issuers, market makers, treasuries) do.
Protocol fee · 10 bps · split 45 / 45 / 10
Stakers · 45%
Protocol-fee revenue (in CCD) is used to buy CCDX on the market and distribute it to stakers. More volume = more rewards.
Lock wallet · 45%
Buys CCDX into a 1-year lock wallet. Subject to DAO approval, may be permanently burned — aligning with long-term holders.
Treasury · 10%
Funds development, audits, security operations, ecosystem growth. The runway behind the API itself.
Live on Concordex devnet today — sweeper runs hourly, stakers earn now. See live APR + recent epochs ↗
Shipping in lockstep with Concordium PLTs.
Indicative timing — may shift with protocol upgrades or operational considerations.
Devnet API, swaps, CCDX rewards & demo
Live today on our own Concordium P10 chain. REST /v1/payments + /v1/swaps + /v1/lp/deposit + /v1/stake settling real PLT transfers, vault-held keys via concordium-ops, four pools (EURX/USDX, CCDX/CCD, EURX/CCD, USDX/CCD), 10 bps protocol fee swept hourly into stakers + 365-day lock + treasury, public block explorer, agentic /demo with MCP tools.
Agent registry, anchor LPs & direct pairs
Every Concordex API key registers its operating agent on the Concordium agent registry, linking the on-chain identity to a real-world entity. External anchor LPs (EURR / USDR stablecoin issuers) onboard against the orchestrator. Direct CCDX↔EURX and CCDX↔USDX pairs alongside the live CCD-routed paths. LP positions dashboard, swap-event webhooks, MCP-tool publishing on a public catalogue for agents to discover. Connect-wallet stake form on /stake.
PLT-locks migration, mainnet & x402
When Concordium ships the PLT-lock primitive, swap + LP settlement migrates from treasury-mediated to non-custodial: LPs keep custody, Concordex only holds release-signing authority. API surface unchanged. Mainnet alpha follows for waitlisted projects with SLA + institutional compliance posture. Adds x402 payment-flow support so HTTP-402-style agent invoicing settles natively against /v1/payments without an extra protocol shim.
Tell us what you'd build.
Concordex rolls out in cohorts alongside Concordium's MCP servers and PLT-locks. Early access is gated — specific use cases jump the queue. Drop your details below and we'll come back to you.