Paid vertical on stellar:testnet

RWA intelligence for Stellar-native agents.

Atlas exposes machine-readable endpoints for inspecting Stellar assets, issuer signals, observable restrictions, changes, and wallet eligibility. Access is gated through standard x402 payment challenges.

01 Inspect Resolve Stellar asset identity and issuer metadata.
02 Observe Track restrictions, changes, and public state.
03 Challenge Return exact Stellar x402 payment terms.
04 Settle Verify payment through the Relay facilitator.
05 Return Send hashable intelligence plus receipt context.
Rate card

Paid endpoints.

Atlas is the first useful paid capability in the Relay network. Prices are intentionally tiny while the machine-commerce flow is proven.

$0.001/ call

Inspect

POST/atlas/v1/rwa/inspect

Identity, standard, issuer, and public metadata for a Stellar asset.

$0.001/ call

Changes

POST/atlas/v1/rwa/changes

Recent observations and tracked state transitions for an asset.

$0.002/ call

Compliance

POST/atlas/v1/rwa/compliance

Observable technical restrictions and transfer posture signals.

$0.002/ call

Eligibility

POST/atlas/v1/rwa/eligibility

Whether a wallet meets the observable requirements to hold an asset.

Payment challenge

Unpaid calls return HTTP 402.

The response carries a Stellar x402 payment requirement. The buyer signs locally, the facilitator verifies and settles, then Atlas returns the paid response. Steps 1–2 run live from this page.

1
Agent requests the resource POST to a paid Atlas endpoint with no payment header.
Live here
2
Atlas answers 402 Response includes the Stellar x402 payment requirement.
Live here
3
Buyer signs locally The agent's wallet signs an exact Stellar payment. Keys never leave the buyer.
Documented
4
Facilitator verifies and settles Relay proxies /x402/verify and /x402/settle to the facilitator.
Documented
5
Atlas returns the paid result 200 with the intelligence payload plus request and response hashes.
Documented
IDLE
GET the payment terms without paying anything.

Press Request 402 to call
POST /atlas/v1/rwa/inspect with no payment
header and read the challenge Atlas returns.
Facilitator support
Reproduce with curl
curl -i -X POST https://atlas.relayx402.xyz/atlas/v1/rwa/inspect \
  -H 'content-type: application/json' \
  -d '{"asset":"C..."}'
Response shape

Every paid call returns the same four blocks.

Structured, hashable, and safe to store. Agents can diff two responses over time without re-parsing prose.

Identity Contract, standard, issuer, and public metadata
State Reachability, transfer posture, technical restrictions
Changes Recent observations and tracked state transitions
Receipt Request hash, response hash, x402 payment metadata
Boundaries

Technical facts, not advice.

Atlas reports observable technical state. Reading the boundary correctly is part of using it correctly.

In scope

What Atlas provides

Observable technical facts and machine-readable state, built for agents that need structured RWA context before taking the next workflow step. Every field is derived from data the network already exposes.

Out of scope

What Atlas does not provide

Atlas does not provide legal advice, compliance approval, investor suitability, custody, brokerage, or asset endorsement. A clean Atlas response is not a permission to transact.

Route to Atlas through Relay.

Atlas is discoverable in the Relay catalog with capability, price, network, and reliability metadata, so an agent can select it under policy instead of hard-coding it.