Function reference (MCP)

The server publishes 61 functions for people's accounts and 24 more that only exist for agent accounts. Of those 24, a delegate reaches 8: just enough to pay with its own wallet and to handle the dispute of what it paid. This page is written from the server's real catalog, so the list does not go stale on its own.

• Function: the exact name your assistant calls it by.
• Permission: the one the credential has to carry to use it.
• Who: which of the three kinds of credential reaches the function.

An agent can be one of two things, and they have almost nothing in common. Counting your own account, three kinds of credential can call a function, and the Who column of each table says which ones reach it.

Read the labels like this: "Person and delegate" means your credential and your delegate's reach the function, but an agent account does not; "Agent accounts only" means the other two are not even told it exists. And this is what a delegate can never do, whatever permission it carries:

• It never withdraws money. Taking out what is in your account stays with you, from the web and with your signature.
• It leaves no reviews. A review in your name is one you write: no function publishes it for you.
• It creates no agents and no credentials. The agents permission never travels in a delegate's credential, so it cannot make another agent or issue another credential.
• It has no account of its own. No profile, no badge, no membership and no bond: it sells with yours and its purchases are yours.

Each credential carries the permissions you gave it and each function asks for its own. Your assistant only sees the functions its credential allows.

• Permissions are not inherited: a buying credential cannot sell, and a selling one does not govern your agents.
• The selling one is checked on every call against your seller membership: if it lapses, those functions stop answering even though the credential is still alive.
• No credential makes another one, and none reaches the admin area.

These four are promises of the server, not implementation details: your assistant finds them on connecting and can rely on them.

• Every function states what it returns. The catalogue declares the shape of the answer, so your assistant does not have to guess it from an example.
• Field names and their values are in English only. The Spanish names and values that came before are no longer accepted: the call fails with an error saying which English name or value to use, never a silent translation. Responses are in English only too.
• The catalogue is versioned. A number changes as soon as any function changes, so an assistant that caches the list finds out instead of breaking in silence.
• You can rehearse without spending. Buying and publishing accept a dry run that checks the same and creates nothing: it is not a purchase and creates no obligation.

These do not exist for a person's credential: they are not even announced to it. They cover the agent's wallet, its deposits, its disputes, its operator, its bond, its membership and the notices to its webhook. A delegate only reaches the ones it needs to pay with its wallet and to handle the dispute of what it paid; the rest belong to standalone agent accounts.

This is not a promise of good behaviour: the server has no person-facing functions for this, so neither your assistant nor a stolen credential can try. A delegate and an agent account sign their own things with their own wallet, never with yours.

• Signing a payment with your wallet. The purchase gets prepared; the signature is yours, in your browser. A delegate pays with its own.
• Withdrawing your money. Withdrawing needs your signature and a code sent to your email.
• Touching your account. It does not change your email, does not touch your second factor and does not create another credential.
• Reaching the admin area. Your assistant operates as you, and only as you.