Payment rails for humans & agents

Make every request
count.

Per-request cost metering and wallet-to-wallet USDC settlement on Base, the chain built by Coinbase.

  1. VXP GLOBAL · receipt
  2. 10 × GTA VI intel items GET
  3. price quoted · USDC on Base 402
  4. signed by the buyer’s wallet SIG
  5. paid wallet to wallet · Base PAY
  6. resource delivered 200
  7. payment on BaseScan tx
  8. no funds or keys held custody

200 / Settled

Explore the stack

Agents are buying software
and services now. Very little was built for them.

  • costs · opaque
  • settlement · human-only
  • ui · unverified

Every checkout on the web assumes a person with a card and a screen. An agent has neither. VXP Global builds the tools it needs instead: a price it can read, a payment it can make, a receipt a person can check.

Every request ends on a receipt.

An agent asks, gets a price, signs, and pays. The payment settles wallet to wallet in USDC on Base, in public, where anyone with the link can open it. Here are four of ours.

Token Oasis runs on these rails.

live

Our agent-friendly marketplace: people and AI agents discover tools and content, pay per fetch over x402, and consume instantly. It runs on the VXP Global stack in production today — the rails carry our own product first.

Explore Token Oasis
tokenoasis.com

NEWS PACK · MARKETS

Today's markets intelligence

$0.005 / fetch Pay with x402
cost $0.0003 · vxp-cost settled on Base · vxp-api

Two columns. One operator.

An agent that spends but cannot earn is a cost center. One that earns but cannot cap its spend is a liability. VXP Global runs both columns, and both run on our own products first: the spend side meters our agent fleet, the serve side prices our own storefront.

SPEND

metered, capped, signed
  • vxp-route

    our fleet

    Local-first routing with quality gates. Secrets redacted before egress, daily budget caps, HMAC-signed audit log. It runs our own agent fleet; it deploys into your VPC.

  • vxp-cost

    live

    Token and USD cost truth, cache- and reasoning-aware, across 34 models from 5 providers. Public GET — no key, no signup. Open the live feed.

  • Velo · MCP

    preview

    Our MCP concierge, metered on the same rails we sell. Five read-only operations today — health, pricing, news brief, intel items, intel topics — and the roster grows as the API does. A preview because it is one: it answers what it can verify and says so when it cannot.

SERVE

priced, charged, settled
  • x402

    private beta

    HTTP-402 micropayments in USDC on Base. Request → 402 → pay → serve, wallet-to-wallet: VXP Global holds neither the funds nor the keys. Open a settlement on BaseScan.

  • Token Oasis

    live

    Our marketplace: people and agents pay per fetch in USDC with passkey checkout — no subscriptions, no surprise invoices. It runs on the VXP Global stack in production today.

  • vxp-catalog

    beta

    The catalog behind Token Oasis: resources gated per use, with entitlement tracking and replay protection, and an agent-readable projection of the same shelf. Ships with the Token Oasis rollout.

One signed audit trail. Debits provable. Credits receipted.

One paid request, stage by stage.

The trace at the top of this page performs the loop once. These are its six stages, the component each one ends in, and what state that component is actually in — read from the same product record the rest of the site reads.

  1. Discover vxp-api live
  2. Request vxp-catalog beta
  3. Pay vxp-catalog beta
  4. Settle vxp-treasury beta
  5. Attribute vxp-cost live
  6. Render slabz-elements coming

We run this loop on our own fleet too: vxp-route meters what our agents spend against the same cost tables the serve side prices with.

What each of these rests on.

Every row below is either backed by an artifact or marked as not being one. Proofs held privately say so, rather than linking somewhere you cannot follow.

view as:
funded settlement: first proof proven · internal

The first end-to-end capture of a funded request on Base mainnet.

the capture · verified internally 2026-04-23

A proof window on mainnet, with real funds — ours, not a customer's. It establishes that the rail works, not that anyone has used it.

nonce-replay: rejected proven · internal

A settled payment cannot be replayed. Rejection is enforced by the database, not by a check — two attempts at the same payment cannot both succeed.

the replay proof · verified internally 2026-04-24

signer isolation: enforced proven · internal

The service that answers requests cannot hold the keys that move funds. That separation is built in, not configured.

the isolation proof

reconciliation: no new charge proven · internal

Settlements can be reconciled against what is already on chain, so verifying the books never costs anyone a payment.

the reconciliation proof

abuse controls: enforced live

Anonymous and paying callers are metered separately, at the edge and in the service. The thresholds are not published.

metering and edge controls

public settlement: on chain proven

A settled x402 request anyone can open: 0.05 USDC on Base mainnet, block 48390957.

the transaction on BaseScan 2026-07-09

Our own wallet, dogfooding our own product. It proves the rail settles on mainnet; it does not claim anyone else has bought anything.

custody: none refused

Settlement moves wallet-to-wallet. VXP Global holds neither the funds nor the keys — there is nothing here to freeze, lose, or run away with.

prompts: never transit VXP Global refused

We meter usage, not content. Deployment is your VPC; the prompts do not come to us.

SOC 2 planned

Planned.

There is no report to show and none is implied. When there is one it appears here, dated.

Who runs VXP Global: the timeline, the receipts, and three open seats.

What an agent can ask us.

Velo is our concierge on vxp-api-mcp-server — the same tools an agent gets, not a description of them. Read-only, and free where it says free.

vxp-api-mcp-server probed 2026-08-24

Velo reads this from our own MCP server. Statuses are from the last probe, and dated for that reason — three of these are free by design and not reachable without a key today.

toolendpointcostanon
vxp_get_pricingGET /api/v1/pricingfreeanswers
vxp_get_healthGET /healthfreenot public yet
vxp_get_news_intel_topicsGET /api/v1/news-intel/topicsfreenot public yet
vxp_get_news_intel_itemsGET /api/v1/news-intel/itemsfree ≤5not public yet
vxp_get_news_briefGET /api/v1/news-intel/briefthinnot public yet

Shown rather than hidden: the gap is a deployment state, not a capability claim.

The same facts, both ways at once.

An agent does not have to read this page. Everything on it is also published as JSON at one URL — and both sides below render from a single live fetch of that URL, so they cannot disagree. Drag the seam.

GET /api/capabilities one source · two renderings

Reading the manifest…

Three URLs. No scraping, no HTML parsing, no guessing at selectors.
surfacewhat it carrieslive
/api/capabilitieswho we are, what we run, which protocols·
/llms.txtthe site in plain text, sized for a context window·
/api/statuswhat is answering right now, and what is not·

Which column do you need first?

Same operator, same audit trail. Start with the side that's on fire — we wire the other when you're ready.

Counted, not estimated. Budget-aware routing cut our cloud spend ~70% against sending the same requests to Claude Sonnet — measured on our own agent fleet, from our usage ledger. Cheaper tiers trade some quality. source: internal fleet · method: vxp-cost + vxp-route

Cost & Control (in your VPC)

spend

Every token your agents spend: metered, capped, redacted, signed — inside your perimeter. Your cloud, your keys, our operations.

Scope a deployment

Agent Commerce

serve

Endpoints that charge. x402 + USDC on Base. Private beta — proven end-to-end on mainnet.

Scope an integration