AI AGENT STORE / SERVICES

INFRASTRUCTURE FOR THE AGENT ECONOMY

Operational logs services for AI agents

Retrieve recorded events to investigate agent and application behavior.

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 operational logs for your task

Choose the dataset and time range that can answer a specific operational question.

Before you proceed: Check ingestion coverage before interpreting an empty result.

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

FIND THE MISSING CAPABILITY

Services with Operational logs

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

Hookdeck Event Gateway ↗

Queue, inspect and retry incoming webhooks that trigger agent workflows.

Before you connect

Create an account and project, connect a source to a destination, and configure incoming webhook signature checks and destination authentication. Select throughput and retention appropriate to the workflow.

Our integration playbook
Make event retries safe before connecting them to agent actions

Inspect setup, billing & access →

Permit MCP Gateway ↗

Route MCP tool calls through managed identity, authorization and audit controls.

Before you connect

Create a gateway organization and host, connect the intended MCP servers, configure user and agent identities and assign tool access. Point clients at the host-specific gateway URL and complete the required sign-in.

Our integration playbook
Check the actual tool behavior behind each access tier

Inspect setup, billing & access →

Sauce MCP ↗

Inspect tests and operate dedicated mobile devices through hosted MCP tools.

Before you connect

Create a Sauce Labs account and choose the required product entitlements. Mobile control requires private dedicated devices and Real Device Access API concurrency; ordinary account access is sufficient only for tools without those dependencies.

Our integration playbook
Confirm the device entitlement before scheduling a reproduction

Inspect setup, billing & access →

Pipecat Cloud ↗

Deploy and scale voice-agent sessions on managed infrastructure.

Before you connect

Create an account and the intended organization, activate billing and configure the application’s model-provider secrets. Prepare an agent image or Dockerfile and choose deployment capacity and transport.

Our integration playbook
Test the full session lifecycle before scaling voice traffic

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.