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.
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
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
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
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
Create a Workspace in the intended region, ingest an authorized dataset and prepare query endpoints. Issue a resource-scoped token or appropriately restricted JWT and set a usage budget.
Our integration playbook Give the agent a scoped analytical question and a known data window
Create a cloud account and cluster, import an authorized collection and configure its vectorizer. Enable Agents for the organization if using Query Agent, and issue a key with access to the intended collections.
Our integration playbook Validate retrieval and access boundaries before asking for summaries
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
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.