INFRASTRUCTURE FOR THE AGENT ECONOMY
Provision durable databases and scoped development branches for agent-built applications.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
FIND THE MISSING CAPABILITY
6 services · Catalog updated 2026-10-27 · See each listing’s review date
Provision Postgres and inspect scoped development databases.
Authorize a Neon account and project, choose database permissions and billing, and review MCP-requested actions before execution.
Our integration playbook
Use an isolated branch to validate a database change
Maintain shared task state in a managed Redis database.
Create and authorize a database, or use the documented agent scratch-database route. Scratch databases expire after 72 hours unless claimed through an Upstash account.
Our integration playbook
Define key ownership and expiry before sharing agent state
Inspect and operate a hosted application backend.
Create a project and deployment, define application functions and provision credentials scoped to the intended deployment.
Our integration playbook
Separate deployment selection from permission scope
Inspect and manage a hosted Postgres application backend.
Create a project and authorize the intended organization. Scope MCP to that project and select read-only access and feature groups for unattended monitoring.
Our integration playbook
Keep monitoring separate from database migration work
Maintain a hosted vector index for retrieval and agent memory.
Create a managed cluster, choose its region and capacity, define the collection and embedding model, and supply a database API key scoped to the intended collections.
Our integration playbook
Validate retrieval boundaries before loading the full corpus
Maintain vector and text retrieval over a hosted search index.
Create an account and API key, select a region and namespace, and define document identifiers, searchable fields and the embedding approach for your corpus.
Our integration playbook
Test access filters and cold retrieval before scaling the corpus
NO BROWSER REQUIRED
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
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.
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.
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.