Back MyApi
OPEN BETA

Your agents shouldn't have your passwords.

MyApi is a personal API gateway that sits between AI agents and your accounts. Agents hold scoped tokens instead of your passwords; the real credentials for 228 connected services stay encrypted in the vault, and every call is monitored, rate-limited, and audit-logged.

220+ services Live monitoring & limits MCP-native
app.myapiai.com
MyApi dashboard — live device activity, API calls, calls by service
Dashboard LIVE
API CALLS · 7D
2.6k
ACTIVE DEVICES
3 / 7
ERROR RATE
0.1%
RATE-LIMITED
0
CALLS BY SERVICE
Gmail Gmail 519
GitHub GitHub 122
Facebook Facebook 96
Elevenlabs Elevenlabs 90

Connect once. Every agent gets exactly the access you choose — and nothing more.

Agents get scoped tokens. Your real credentials stay sealed in the vault — never seen, never shared.

WHY IT MATTERS

The security community has already named this problem.

“Access to your private data — one of the most common purposes of tools in the first place! … Exposure to untrusted content … The ability to externally communicate in a way that could be used to steal your data.”

— Simon Willison, defining “the lethal trifecta” for AI agents (2025). MyApi narrows the trifecta at the middle: least-privilege scopes, cross-service data-flow policies, and human approval on risky egress shrink the blast radius of a hijacked agent. Scopes alone do not eliminate injection — an agent authorized to read one service and write another can still exfiltrate within its grants, which is exactly why egress and intent controls exist.

“An LLM-based system is often granted a degree of agency by its developer — the ability to call functions or interface with other systems … to undertake actions in response to a prompt.” The risk stems from excessive functionality, excessive permissions, or excessive autonomy.

— OWASP, LLM06:2025 “Excessive Agency”, Top 10 for LLM Applications. MyApi is the permissions layer: each agent gets exactly the functions and scopes you chose, nothing more.

“The principle that a security architecture is designed so that each entity is granted the minimum system resources and authorizations that the entity needs to perform its function.”

Works with your stack.

220+ services. MyApi holds the OAuth and the keys — agents never see them.

Browse the full catalog of 228 services →
PERSONAS

Scope, role & tone. In one profile.

Build a persona once — skills, knowledge, and a scope ceiling — and assign it to any agent. Or skip it: a plain scoped token works on its own.

MyApi personas — AI profiles available to assign to agents
Skills it can run
Knowledge it draws on
Scopes it can't exceed
SCOPE RESOLUTION

Every call, checked. Every time.

Token, persona ceiling, service grant — the narrowest wins. Out-of-scope calls never reach the service.

GET /calendar/events calendar:read ✓
POST /repos/issues github:write ✓
GET /billing/cards out of scope ✕
MONITOR & LIMIT

Watch every call. Cap the ones that matter.

Live metrics per agent and per service. Set rate limits, get alerted on unusual volume, and pause or revoke any agent in one click.

2.6k
API calls · 7d
0.1%
error rate
0
rate-limit hits
3 / 7
active devices
SECURITY

Built like a vault. Documented like one.

Credentials are encrypted with AES-256-GCM before they touch the database; scoped tokens are stored hashed; every API action lands in the audit log with agent attribution.

AES-256-GCM
vault encryption at rest
PBKDF2 · 600k
key derivation iterations
100% audited
every call logged & attributed
Injection scan
inbound content screened
Read the full security practices →
BACKUP & RESTORE

Your brain, backed up.

Snapshot everything that makes your setup yours — and restore it anytime, or move it between workspaces without losing a thing.

Personas Skills Knowledge base Memory
MYAPI MCP

One MCP server. All your services.

Point any MCP client at your gateway. Every service surfaces as tools, already scoped.

$ claude mcp add myapi \
    https://gw.myapiai.com/mcp --token $MYAPI_TOKEN
✓ connected · 220+ tools · scoped by token
Claude Code OpenClaw Hermes Claude Desktop Cursor any MCP client
Setup guide, device approval & troubleshooting →
TWO-MINUTE DEMO

Watch it work.

Open the demo page — all seven steps written out →

Questions, answered.

Do my agents ever see my real credentials?

No. Credentials are encrypted with AES-256-GCM and never leave the vault. Agents get scoped tokens; MyApi proxies and signs each call — no password, token, or secret is ever exposed. See the full security practices.

What is a persona?

A reusable AI profile — scope, role & tone in one. It bundles skills, knowledge, and a scope ceiling. Assign it to many agents, or none: a plain scoped token works on its own.

How does scope resolution work?

Each call is checked against the token, the persona ceiling (when attached), and the service grant. The narrowest wins; denied calls never reach the service.

Can I monitor and rate-limit what agents do?

Yes. Every call is metered per agent and per service. Set rate limits, get alerts on unusual volume, and pause or revoke any agent in one click.

Can I back up my personas, skills, and knowledge?

Yes. Snapshot personas, skills, knowledge base, and memory, then restore anytime or move them between workspaces — nothing is locked in.

Does it work with Claude, MCP, and other frameworks?

Yes — MCP-native and plain REST. Claude Code, Claude Desktop, Cursor, OpenClaw, Hermes, custom agents — anything that can hold a bearer token or speak MCP. Setup guide in the docs.

What does the beta cost?

Nothing — open beta, no credit card. Bring your own model keys for free, or use platform credits.

Where are the developer docs and API reference?

Human docs live at /docs — auth flows, token lifecycle, REST examples, MCP setup. Machine-readable: /openapi.json (OpenAPI 3), /llms.txt (agent instructions), /auth.md (agent registration).

Which services are supported, exactly?

228 services today — Gmail, GitHub, Slack, Notion, Stripe, Jira, and more — connected by OAuth, API key, or instance URL. Browse the full catalog.

How is my data actually secured?

Credentials are AES-256-GCM encrypted at rest with PBKDF2 (600k iterations) key derivation; scoped tokens are stored bcrypt-hashed; every API action is audit-logged with agent attribution; inbound content is scanned for prompt injection. Full details at /security.

Can I use MyApi with a team?

Yes. Workspaces partition services, tokens, and audit history; invite members with role-based permissions, and move personas or knowledge between workspaces. SSO, SCIM, and seat billing exist for organizations — pricing is finalized after beta.

OPEN BETA — NO CREDIT CARD REQUIRED

Free while we build it with you.

Every capability is unlocked during the open beta. Commercial packaging will be set once real usage teaches us what matters — no fake certainty before then.

LIVE
FOUNDING BUILDER BETA
$0 free during beta

Your plan while MyApi is in open beta.

All current features open
All service connections available
Direct product feedback loop
No credit card needed
Join the beta →
WHAT YOU CAN TEST NOW
Open beta capabilities

Use the full control layer before packaging is finalized.

Scoped token bootstrapping
Personas, skills, knowledge & memory
Service access, approvals & audit logs
Machine access via AFP & MCP
See what's included
AFTER BETA
TBD not finalized

Packaging set once beta usage teaches us what matters.

Packaging informed by real usage
Limits & seats from observed patterns
Commercial plans announced after beta
No fake certainty before then
Follow progress

During the open beta, every capability is unlocked on your account. Commercial plans — including team and enterprise options — will be announced after beta.

Access, not passwords.

Open beta. First service connected in two minutes.

Join the beta →
Free to start · No credit card