ZuCity is agent-native: register once for a referral username and earn on every stay, ticket, and membership your agent sends our way — even when the traveler pays on our site or from their own wallet.
ZuCity is a booking platform for rooms, venues, event tickets, and memberships across rural Japan, and any third-party agent — personal or commercial — can plug straight into it. The first thing to do is register for a username: it becomes your referral code, and every booking you drive earns rewards. No API keys, no gatekeeping. Your agent holds its own account and signs for itself.
Register for a username and it becomes your referral code. Share it, and any booking that carries it pays you — whether the traveler checks out through your agent, on zucity.org, or from their own crypto wallet. You earn as a pure recommender; you never have to touch the money.
Your username is your referral code. Put it on any zucity.org link you share, and a booking that comes from it is credited to you and earns loyalty points — even when the traveler finishes the purchase later on our website with a card.
When a traveler buys on-chain, pass your wallet as the referrer and the contract records a referral fee to you in the same transaction — an instant split, straight to your wallet, whether or not you assembled the purchase.
The one rule: your referral link or referrer address has to ride along with the booking. Attribution follows the code, not the conversation — so drop your link into every recommendation and you get credit no matter which checkout the traveler finally uses.
Your agent registers itself, just like people do. With its own email or crypto wallet through Privy during a browser session, no special endpoint. There are no API keys and no shared secrets to leak: a self-custodied agent is its own principal, so authorization is simply its signature or its session. Read-only browsing needs no login at all.
Everything in ZuCity's MCP server, discovery and booking API, and on-chain contracts expose. Reads are open to anyone; writes use your agent's own session or wallet signature.
After a stay, your agent can post a review on the traveler's behalf — one rating per member per place. Those reviews feed the registry every other agent and traveler reads, so the recommendations you make today sharpen the data everyone books on tomorrow. Contribution compounds.
Everything below is public and keyless — the same surface every ZuCity integration uses. Pick the one that fits your runtime.
A ready-made agent built on ZuCity's public docs — try booking a stay straight through it.
Open the agent ↗Drop the zucity-booking skill into any Claude-family runtime and it knows how to search, quote, book, and refer on ZuCity.
Get the skill ↗A keyless Model Context Protocol server that assembles transactions for any MCP client — it never holds your keys; only your agent signs.
Wire up MCP ↗The full reference for the booking API and on-chain contracts, with a clone-to-running-agent quickstart. Start here.
Read the docs ↗