AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

Secrets management services for AI agents

Supply credentials to agent workloads through managed stores and scoped access.

Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.

163 available services15 capability categoriesOpen discovery · no login

Choosing secrets management for your task

Compare token scope, expiry, delivery, audit retention and rotation. Prefer the existing secret manager when it already meets the workload’s needs.

Before you proceed: Verify environment and permissions without printing values; runtime injection does not hide secrets from the receiving process.

AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.

FIND THE MISSING CAPABILITY

Services with Secrets management

2 services · Catalog updated 2026-11-10 · See each listing’s review date

Doppler ↗

Supply scoped credentials to agent workloads through managed secrets, CLI and MCP.

Before you connect

Create a project and a config containing only the required credentials. Have an authorized administrator issue a suitably scoped token, choose its expiry and configure the agent runtime. The MCP server requires Node.js 20 or later.

Our integration playbook
Match credential scope to the workload before launching it

Inspect setup, billing & access →

Descope Agentic Identity Hub ↗

Give agents policy-controlled access to third-party credentials and delegated integrations.

Before you connect

Create a project and Connection, configure provider credentials and consent, then define agent identity, tenant membership and access policies. Users must connect accounts that require their consent.

Our integration playbook
Keep the caller identity attached to each credential request

Inspect setup, billing & access →

Explore related capabilities

Browse all service tags →

NO BROWSER REQUIRED

Discover. Inspect.
Connect.

Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.

GET /api/agent-services?capability=email
GET /api/agent-services?interface=mcp
GET /api/agent-services?payment=x402-wallet
GET /api/agent-services?payment=mpp-wallet
GET /api/agent-services?payment=no-payment
GET /api/agent-services?id=e2b

Full catalog: /data/agent-services.json

Manifest: /.well-known/agent-services.json

Choose your next service with the facts in hand.

Find the tools you need

You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.

Check what you need from your owner

Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.

Confirm your payment path

Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.