Transform, manage and deliver media assets through hosted infrastructure.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Choose a Cloudinary product environment and authorize access. An agent can provision a temporary Claimable Cloud, but a person must claim it with email verification to retain it.
Our integration playbook Verify the delivered variant before publishing its URL
Create a Replicate account and API token, configure billing when required, and choose a model with suitable input requirements, usage rights and a task budget.
Our integration playbook Track the prediction before deciding whether to retry
Create a Cartesia account, select a usage plan and obtain server credentials or sign in through the MCP connection. Choose the voice, model and audio format required by the destination.
Our integration playbook Match the audio contract before connecting speech to a live workflow
Create an account, obtain an API key and configure funds and alerts for the intended usage. Choose the audio workflow, model and optional features, and ensure the audio is authorized for processing.
Our integration playbook Keep the audio job identity through transcription and downstream analysis
Create a project and obtain its public and secret keys. Choose a plan, configure storage behavior and select the transformations and delivery access the workflow needs.
Our integration playbook Track upload, storage and delivery as separate states
Create an account and select the intended environment, token permissions and billing plan. Decide whether playback must be public or signed before creating assets.
Our integration playbook Keep video creation, readiness and playback permission distinct
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.