Milypay: Australian data for AI agents over x402, settled in AUD on Solana

Most x402 providers are horizontal: crypto quotes, email, OCR, generic search. That catalog is useful and still incomplete the moment an agent needs to operate in Australia — verify an ABN, clean a G-NAF address, price an AusPost parcel, or check a BSB before a payout.

Milypay is the local layer for that gap. It is an x402 service provider for the Australian market: pay-per-call access to Australian government and commercial data, settled in AUD-denominated stablecoins on Solana, discoverable on Pay.sh under the milysec/* namespace. No API keys. No signup. Payment is the auth. Parent studio: Milysec.

Click to zoom

If you already know the wire protocol from our x402 primer and the facilitator story in PayAI, this article is the product map: what Milypay sells, how agents call it, and why AUD settlement matters.

The gap it fills

The site's own framing is blunt: dozens of providers on pay.sh, zero that speak Australian until a local namespace shows up. Agents building for AU commerce, KYB, logistics, or super need rails that:

• return structured AU identity and address data,
• price in AUD without a USD FX round-trip,
• authenticate by payment instead of a human-issued API key.

That is the DevRel pitch for ANZ builders and anyone shipping agents that touch Australian counterparties.

How payment works

1  Agent  GET https://api.milypay.xyz/au-business/abn/{abn}
2  Host   HTTP 402 Payment Required
           + PAYMENT-REQUIRED challenge
           (price, asset, network=solana, pay-to)
3  Wallet / x402 client settles via PayAI facilitator
4  Retry  with PAYMENT-SIGNATURE (or X-PAYMENT)
5  Host   HTTP 200 + JSON body

Confirmed live behaviour on the API host: unpaid calls return 402 with CORS exposing PAYMENT-REQUIRED / PAYMENT-RESPONSE and allowing PAYMENT-SIGNATURE. Price string on a sample ABN lookup: micropayment in USDC / USDT / AUDD / AUDM / dAUD.

Two hosts, two modes — important for workshops:

• Paid production: https://api.milypay.xyz/... — real x402.
• Free try: https://milypay.xyz/api/... and the live demo — same data shapes, per-IP rate limited, no wallet required.

# Free try (website host)
curl -sS "https://milypay.xyz/api/au-business/abn/51824753556" | jq .

# Paid path (agents) — expect 402 without payment
curl -sS -D- "https://api.milypay.xyz/au-business/abn/51824753556" -o /dev/null

# Pay.sh CLI shape (catalog namespace)
npx pay.sh call milysec/au-business/abn 51824753556

Service catalog (milysec/*)

Base URL: https://api.milypay.xyz. Machine-readable discovery: /.well-known/x402. Full agent guide: /agents.md.

Example endpoints agents actually hit:

GET /au-business/abn/{abn}
GET /au-business/acn/{acn}
GET /au-business/search?name=
GET /au-company/acn/{acn}
GET /au-company/search?name=
GET /au-company-report?acn=
GET /au-address/validate?q=
GET /au-address/search?q=
GET /au-address/geocode?q=
GET /au-super/abn/{abn}
GET /au-weather?q={address}
GET /au-weather?lat=&lng=
GET /au-postage?from=&to=&weight=
GET /au-postage?country=&weight=
GET /au-bsb/{bsb}
GET /au-bsb/search?q=

Settlement: why AUD-native matters

Default story on the marketing surface is AUDD — a 1:1 AUD-backed, AFSL-regulated digital dollar live on Solana. The discovery manifest is broader and honest about catalog reality: AUDD, AUDM, dAUD for AUD-native settlement, plus USDC and USDT for pay.sh compatibility. Facilitator: https://facilitator.payai.network. Network: Solana mainnet.

For Australian operators the point is not ideology. It is accounting. Global x402 demos settle in USD stablecoins and force FX, reporting noise, and "what was that 0.002 USDC in AUD yesterday" into every board pack. AUD-native settlement keeps agent spend in the same unit the business already books.

Deeper AUD stablecoin context on the product site: milypay.xyz/stables. Protocol context: x402 on Solana, PayAI facilitator, stablecoins on Solana.

How agents integrate

1. Raw HTTP 402 — any x402-aware client; no SDK required.
2. Pay.sh CLI — npx pay.sh call milysec/... handles challenge + wallet approval.
3. Pay.sh MCP — drop into Claude, Cursor, or other MCP hosts; tools auto-priced.
4. SDK — TypeScript/Python x402 client that wraps fetch and retries with payment (product docs).

Agent-first docs are first-class, not an afterthought: agents.md, llms.txt, llms-full.txt, and /.well-known/x402 are all on the apex domain. That is the same pattern we want every Solana API product to ship.

Stack at a glance

Protocol      x402 (exact scheme)
Facilitator   PayAI
Catalog       pay.sh  ·  namespace milysec/*
Settlement    Solana
Assets        AUDD (default story) · AUDM · dAUD · USDC · USDT
API host      api.milypay.xyz   (paid)
Try host      milypay.xyz/api/* (free, rate limited)
Studio        Milysec (milysec.com)
Sources       ABR · ASIC · G-NAF · ATO super · BOM/Open-Meteo · AusPost · AusPayNet

Builder / DevRel angles

• Workshop demo: free apex path for ABN lookup, then show the 402 challenge on the API host without forcing a paid call.
• Agent KYB lane: ABN + ASIC + address validation is a concrete multi-tool flow for onboarding AU merchants.
• ANZ narrative: Solana agent payments stop being abstract when the endpoint is a real Australian register.
• List your API: product invites other Australian APIs onto the same rail via contact.
• Compose with Gecko: comprehension layers (see Gecko) can sit in front of any OpenAPI; Milypay is the paid AU data plane those agents settle against.

Honest scope

• Micropay prices and asset lists move — treat /.well-known/x402 as source of truth at call time.
• ASIC extracts are a different cost tier than open-data company lookups; do not teach them as the same product.
• Free demo endpoints are for exploration, not production SLA.
• This is a commercial Milysec product. Coverage here is technical ecosystem documentation, not a grant endorsement.

Resources

• Product: milypay.xyz
• Agent guide: /agents.md
• Docs: /docs · demo: /demo · stables: /stables
• Discovery: /.well-known/x402
• API: https://api.milypay.xyz
• Catalog: pay.sh · namespace milysec/*
• Facilitator: PayAI x402 docs
• Spec: x402.org
• Parent: milysec.com · X @milysec
• Related on devrels.xyz: x402, PayAI, build an x402 seller, Gecko

Bottom line

x402 is only as useful as the APIs that speak it. Milypay is the Australian-data answer on Solana: real registers, AUD-native settlement, pay-per-call, no key ceremony. If you are teaching agents that can operate in ANZ, this is the concrete endpoint list to put in the lab — free path first, 402 path when they are ready to settle.