Genieby Payman

Build with Genie.

Genie is an agent. Your software reaches it through its MCP server at https://genie.paymanai.com/mcp, says what the person wants in their own words, and reads back what happened. Genie decides how, or whether, it happens: it picks the rail, resolves the account and the recipient, and applies the limits the person set.

An agent you built

Connect Genie to your own agent

  1. Point your MCP client at https://genie.paymanai.com/mcp over Streamable HTTP. For example, in Claude Code: claude mcp add --transport http genie https://genie.paymanai.com/mcp.
  2. Let the client sign in. On the first call Genie answers 401 with the OAuth resource metadata; a compliant client discovers the authorization server, opens Genie’s sign-in page, and returns with a token. Register your redirect URI with Payman first; Genie only sends people back to addresses it knows.
  3. Running a service rather than a person’s client? Use an integration key instead of OAuth and pass the person’s customer id and email in the headers described below. Their first request returns a Connect link they open once.
  4. Call ask_genie with the person’s words. Do not fill in a payment form or pick an account; describe the intent and read the status.

The contract

What your agent gets

Endpoint
https://genie.paymanai.com/mcp, MCP Streamable HTTP. Server name genie-mcp.
Tool
One tool: ask_genie. Input request (what the person wants, in their words), optional context and conversation. Output status and message.
Statuses
done Genie answered or acted · needs_input relay the message and call again with the conversation value · needs_approval the person approves on Genie’s own surface · refused outside their limits, and the message says which.
Sign-in
OAuth 2.1, authorization code with PKCE (S256), public client. Scope yuki:ask. Discovery: https://genie.paymanai.com/.well-known/oauth-protected-resource/mcp names the authorization server; its metadata names the authorize and token endpoints.
Unauthenticated calls
Return 401 with WWW-Authenticate: Bearer resource_metadata="…", scope="yuki:ask", so a compliant MCP client starts sign-in on its own.
Your own agent, without OAuth
Use a Genie integration key: send x-paygent-mcp-access-key with x-paygent-mcp-customer-id and x-paygent-mcp-customer-email for the person the agent works for. The first call for a new person returns a Connect link they open once.

Using an assistant instead?

Claude, ChatGPT and Grok Bot connect to Genie without any code.