API

These pages describe the browser bridge to Yap Signer and the HTTP routes on this origin. There is no key server here.

Clients

The API is the common interface between Yap applications, agents, wallets, and payment infrastructure. The signer is the authorization boundary under that interface. MCP is not required.

Chrome. Yap Signer, current
iOS. Planned
Android. Planned
Control layer. Planned
Agents. Planned

Those clients meet at the Yap Wallet API. Yap Signer is the authorization boundary under that API. Payment rails and execution come after the signer.

The Yap Wallet API is the common interface for clients, agents, wallets, and payment infrastructure. A call reaches Yap Signer, and the signer is the authorization boundary. Today the API reads public status and asks the extension to sign. The extension still holds the key. Chrome is the current client. iOS, Android, the control layer, and agent execution are not released. MCP is not required.

The Yap Wallet API is not only for the primary wallet. The planned control layer would call that API and coordinate authorized wallets. That fleet is not live.

Yap Wallet APIThe common interface
Yap SignerWallet authority
Payment railsTraditional and crypto
ExecutionClosed for agents

Words

Wallet API. The common programmatic interface for clients, agents, wallets, and payment infrastructure. Today it is the page bridge: public status, and a request the signer may sign.
Signer. The user-controlled authorization boundary. Yap Signer holds the key and stands between the wallet, agents, and payment infrastructure. A request does not receive the key.
Policy. What an agent is allowed to do. A bound set by the person, not access to the primary treasury, and not an open rail.
Control layer. Configure. Authorize. Observe. Planned, and still closed. It would coordinate authorized wallets and payment activity. It would not hold their keys.
Execution layer. Execute. Monitor. Settle. The signer does this for the primary wallet after review. Agent execution, and fiat-to-crypto execution, are closed.

MCP is not part of this interface. An API is enough. MCP could be an optional agent-facing interface later.

Page bridge

A page may send ping and getStatus with postMessage.
The reply stays on this origin and is public status: install, wallet, username, and address.
If Signer is missing, the page links to the Chrome Web Store.

HTTP routes

GET /api/session reads the signed-in email and role.
POST /api/referral/install credits one install of an 8-character referral code.
POST /api/activity records a confirmed swap or send for a signed-in account.

Accounts

Onboarding stores an email, a password hash, and an 8-digit code hash until the code expires.
After the code, the account stores the public username Signer generated, once the typed name matches.
The operator desk can pair that username and clear it later.

Kept off this origin

The site does not invent a username. Signer generates it on the device.
The site does not accept a seed, vault password, or private key.
The site does not unlock the vault, sign, or send.

API