Case Study: Shipping Milypay — x402 Agent Data for Australia

Most Australian data APIs still assume a human with a credit card and a vendor portal. Agents do not have either.

This case study is about Milypay — a product we built and run as Milysec — and the decisions that got it to production. It is not a client anonymisation. It is our own venture, on purpose: studios that only consult drift; studios that ship stay honest.

Live product: milypay.xyz · Studio: milysec.com · Try ABN lookup: ventures page

---

The problem

Australian operators and agent builders need the same lookups every day:

• Business identity (ABN / ACN / name)
• Company records (ASIC open data and official extracts)
• Addresses (GNAF validate / search / geocode)
• Banking (BSB)
• Super, weather, postage quotes

The data exists. The integration shape does not:

1. API keys and seats — fine for a SaaS dashboard, wrong for an autonomous loop
2. USD billing and FX — silly for a two-tenth-of-a-cent Melbourne ABN check
3. No machine-native payment — the agent can call tools; it cannot pay without a human

We wrote about the wider loop in agentic payments in Australian retail and why Australia needs its own stablecoin. Milypay is the concrete rail.

---

What we shipped

Pay-per-call Australian data over x402 on Solana.

Settlement: AUDD, AUDM, dAUD first; USDC/USDT for catalog compatibility.

Auth model: payment is the credential. No API key signup for the core loop.

Pricing shape: about $0.001–$0.004 for common lookups; official ASIC extracts higher. Live 402 challenges are source of truth.

Product update with catalogue and diagrams: Milypay: What Just Shipped.

---

Constraints we designed around

1. Australia-first settlement

If the data is Australian, the unit of account should be AUD. Forcing every agent through a USDC mental model adds FX noise to a sub-cent call. We documented accepted mints on milypay.xyz/stables.

2. Demo host vs paid host

Number one integration bug: mixing paths.

• Demo (throttled, free): https://milypay.xyz/api/...
• Paid: https://api.milypay.xyz/... (no /api prefix)

We made that boring on purpose. Agents fail loudly when hosts are wrong; docs and errors stay stable.

3. Machine-readable failures

Errors return a fixed shape (error, code, brand, docs) so agents branch without scraping HTML. Paid success can attach $receipt and explorer links.

4. Studio dogfood

Milypay is not a slide. It is how we eat our own cooking for client FDE work on agents and payments. That feedback loop is the point of a venture studio, not a body shop.

---

Results (as of ship)

• Live public product and API surface
• CLI + first-party MCP + SDK + HTTP on one protocol
• AUD-native settlement path alongside USDC/USDT
• Studio site integration — live ABN demo on /ventures
• Editorial trail — protocol explainers, stablecoin context, product changelog on this blog

We do not invent vanity MAU charts here. The proof is the endpoint and the receipt.

---

What we would tell a client doing the same class of work

1. Start from the agent’s payment path, not the dashboard. If a human must open a portal, you do not have an agent product.
2. Pick a settlement asset that matches the domain. AU data → AUD stables when you can.
3. Separate demo and paid traffic early. Collapsing them creates silent production bugs.
4. Stable error and receipt shapes beat pretty JSON that changes weekly.
5. Ship a thin vertical (one high-value lookup) before a “full AU data lake.”

That is also how we run forward deployed engagements: outcome first, theatre never.

---

Work with us

If you need agent-payable Australian data, start at milypay.xyz.

If you need the studio on a custom build — agents, Solana, payments, or an internal rail that looks like Milypay for your domain — book a call or email [email protected].