Free
Freeno payment
- 1,000 requests per 30 days
- 30 requests a minute, shared by your keys once quotas are enforced
MERRYMEN / DEVELOPERSAPI v1
YOUR APP. THEIR MERRYMAN.
Give your app
an agent of its own.
Create agents. Set their limits. Start a conversation.
One API, with the entire setup inside your app.
Wallet-owned agentsOn-chain permission limitsBuilt-in chat
your-app / server.tsREST API
// Your interface. Their agent. const agent = await merrymen( "/agents", { external_user_id: "usr_123", name: "Robin" });
202 ACCEPTED · EXAMPLE
{
"id": "pa_…",
"status": "pending_authorization"
}The owner signs. Merrymen runs the worker.
01 / YOUR WORKSPACE
Keys to your next idea.
Give each app its own key. User wallets stay in their control.
Loading your developer account…
02 / PLANS
Start free. Grow into a plan.
Once plans open, every API request counts toward your plan; /meta stays free. Paid plans are paid in $MERRYMEN on Robinhood Chain from the wallet you sign in with.
Crumbs
100,000 MERRYMENper 30 days
- 50,000 requests per 30 days
- 60 requests a minute, shared by your keys once quotas are enforced
Loaf
400,000 MERRYMENper 30 days
- 250,000 requests per 30 days
- 120 requests a minute, shared by your keys once quotas are enforced
Feast
1,000,000 MERRYMENper 30 days
- 1,000,000 requests per 30 days
- 300 requests a minute, shared by your keys once quotas are enforced
Paid plans are coming soon. Until they open, nothing is charged and there is nothing to send.
API plans are paid, unlike the Merry Circle, which you join by holding. Paying moves MERRYMEN out of your wallet, and Merry Circle tiers and hosted energy follow the balance you hold. $MERRYMEN token contract ↗
03 / FROM ZERO TO FIRST CONVERSATION
A few calls. A whole Merryman.
Your backend holds the key. Your user signs the permissions. We run the agent.
Create your first connection
Save your key as MERRYMEN_API_KEY on your server. Create a connection for a user who is signed in to your app. A pending_authorization response means they still need to approve wallet permissions.
// Your backend only. Never put this key in browser code.
const API = "https://ai.merrymen.dev/partner/v1";
async function merrymen(path, body) {
const response = await fetch(API + path, {
method: body === undefined ? "GET" : "POST",
headers: {
Authorization: `Bearer ${process.env.MERRYMEN_API_KEY}`,
"Content-Type": "application/json",
},
...(body === undefined ? {} : { body: JSON.stringify(body) }),
});
const data = await response.json();
if (!response.ok) throw new Error(data.error?.message || "API error");
return data;
}
// Get this ID from YOUR authenticated session.
const agent = await merrymen("/agents", {
external_user_id: currentUser.id,
name: "Robin",
});04 / THE SURFACE AREA
Small API. Plenty of possibility.
BASE URL
https://ai.merrymen.dev/partner/v1POST/agentsCreate a user's agent connection+
Create a user's agent connection. Requires write:agents and your backend’s Authorization: Bearer <key> header.
POST/agents/{id}/challengeRequest wallet authorization+
Request wallet authorization. Requires write:agents and your backend’s Authorization: Bearer <key> header.
POST/agents/{id}/activateInstall permissions & start the worker+
Install permissions & start the worker. Requires write:agents and your backend’s Authorization: Bearer <key> header.
GET/agents/{id}Read actual worker status+
Read actual worker status. Requires read:agents and your backend’s Authorization: Bearer <key> header.
POST/agents/{id}/messagesSend a message to the agent+
Send a message to the agent. Requires chat:agents and your backend’s Authorization: Bearer <key> header.
GET/agents/{id}/messagesRead conversation history+
Read conversation history. Requires chat:agents and your backend’s Authorization: Bearer <key> header.
DELETE/agents/{id}/connectionDisconnect your app+
Disconnect your app. Requires write:agents and your backend’s Authorization: Bearer <key> header.
05 / BEFORE YOU SHIP
Built for a clear boundary.
Keys belong on the server.
Never embed your partner key in browser code, mobile bundles, or a public repository. The browser SDK only prepares wallet permissions.
Ownership comes first.
Derive user IDs from your own authenticated sessions. Every agent needs its owner’s signature before your app can use its private context.
A reply is not a trade.
Chat proposals are not executed automatically. Agent workers follow their signed permissions and configured strategy. No provider available? Chat says so.
Rotate without losing users.
Replace a key to keep the same app ID. Update your backend, then revoke the old key. Disconnecting an app does not stop the underlying agent.