COMPUTE & SANDBOXES · FOR AI AGENTS
Tenderly
Simulate transactions and inspect contract execution in managed blockchain environments.
Use Tenderly’s APIs and hosted MCP tools to examine transactions, traces and Virtual Environments before committing real onchain actions.
Your integration checklist
- Capabilities
- What you need from your owner
- Create a Tenderly account and project, arrange a paid plan and have MCP access enabled through sales. Select the intended project, network and Virtual Environment before running a workflow.
- Authentication
- MCP at https://mcp.tenderly.co/mcp uses OAuth and the account’s permissions. REST project APIs use an X-Access-Key token. Most MCP operations require active project context.
- Your first task
- Confirm the active project and network, then simulate a known transaction and inspect its status, asset changes and decoded trace.
- Billing & payment
- Free provides browser-based tools without API access. Programmatic workflows and MCP require paid access; capacity and included products are agreed with the provider. Simulation avoids onchain gas spending but still uses service resources.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- Simulation depends on the chosen state and overrides; later live execution can differ. MCP summary traces and events can be truncated, requiring deeper trace navigation. A paid-plan restriction can appear as an OAuth loop even after successful sign-in.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Keep simulated state separate from permission to move real assets
Editorial recommendation · Reviewed 2026-10-29
When to choose this service
Choose Tenderly when an agent needs transaction execution evidence and managed test environments tied to blockchain state.
Current chain state, execution simulation, decoded traces and hosted virtual environments require maintained infrastructure and data. Reading contract code alone cannot reproduce a transaction’s concrete state-dependent outcome.
Suggested workflow
- Confirm the project, chain and block or Virtual Environment. Record any overridden balance or storage value.
- Inspect the simulated status, affected assets and failing calls. Navigate deeper when a summary omits part of the trace.
- Compare results with the intended action and retain the simulation input. Obtain the required authority separately before any real transaction.
Acceptance checks before real work
- Check that test balances cannot be mistaken for spendable assets.
- Ensure the selected environment did not change between tool calls.
- Re-simulate against sufficiently recent state before relying on a preview.
If the workflow fails
Resolve active-project and environment errors first. For quota_limit_reached after successful OAuth, check plan access rather than looping through login. Preserve failed traces for diagnosis.