API profile

Tenderly

Tenderly is tracked as a Provider Profile for Web3 simulation, monitoring, alerting, and node RPC infrastructure. Public docs and pricing evidence support the profile, while PubFi Discovery does not assert a PubFi gateway route, adapter certification, payment path, or upstream credential for Tenderly

Coming soonNeeds re-verification

Decision guide

Use it when

Teams that need transaction simulation and debugging context before production changes

Check first

Free API-backed production calls without a paid or console plan

PubFi status

Needs re-verification

The editorial profile remains useful, but its public evidence is degraded. Reverify upstream docs and commercial terms; use the live Registry and runtime OpenAPI for PubFi execution decisions.

Key facts

Auth
API key
Pricing
Freemium
Agent actionability
Editorial revalidation required; runtime status separate
PubFi gateway
Live Registry unavailable
Last verified

Provider-sourced facts

Primary query
tenderly api Source
Primary coverage
Transaction simulation, debugging, monitoring, alerting, and node RPC infrastructure for Web3 teams Source
Free plan boundary
Public pricing says Tenderly Free includes browser UI access and no API access on Free. Source
Commercial fact
Public pricing describes Console and infrastructure features, with capacity, support, and chain count sized in conversation. Source
PubFi status
PubFi Discovery tracks Tenderly as a public Provider Profile only; this profile does not assert a PubFi gateway route, adapter certification, or credential availability. Source

Best fit and tradeoffs

Best for

  • Teams that need transaction simulation and debugging context before production changes
  • Incident-response workflows that depend on alerts, monitoring, and automated response routing
  • Web3 infrastructure evaluations that compare node RPC with developer-tooling features
  • They want a public starting point for evaluating Tenderly API documentation.
  • They need to compare Tenderly against nearby crypto data providers before runtime integration work.
  • They want claim-safe evidence that can be promoted later when adapter certification exists.

Watchouts

  • Free API-backed production calls without a paid or console plan
  • Pure market-data aggregation that does not need simulation or monitoring
  • Teams expecting a PubFi-certified gateway route today
  • Automation-built profiles may have incomplete category, pricing, quota, or endpoint coverage until deeper docs parsing runs.
  • Public docs evidence does not prove credential availability, commercial approval, uptime, or PubFi gateway runtime support.
  • Teams should verify endpoint shape, authentication, quotas, and terms before treating the provider as production-callable.

Why teams choose it

Tenderly API is an automation-built Provider Profile based on public API corpus evidence. It helps teams inspect Tenderly docs, product naming, and on chain state fit before any runtime adapter or commercial approval work begins.

Discovery keeps this page claim-safe: inclusion means public evidence was processed into a Provider Profile, not that PubFi has certified gateway routing, credentials, x402 payment, MCP tooling, or supplier procurement for Tenderly.

What it can cover

Tenderly API on chain state evidence

Unproven
Category
On-chain state
Public status
Requested
Auth requirement
API key
Access review
Not Procurable
Coverage
Ethereum, Base
Output contracts
Chain State Record

Quick start

RESTEndpoint path not listed
Style
REST
Language
HTTP
Method
Not listed
Path
Not listed
Requires auth
Yes
Provider docs
Documentation

PubFi gateway

Live Registry unavailable

PubFi could not verify the active signed Registry generation. Checked-in Discovery content is not execution authority, so this page fails closed instead of inferring a gateway route.

Runtime status
registry_unavailable
Active capabilities
0
PubFi auth headers
Authorization: Bearer <PubFi API key> or X-PubFi-Api-Key: <PubFi API key>
Typed contract
Runtime OpenAPI
  • Retry the live Registry view or inspect the runtime OpenAPI before execution.
  • Do not infer availability from provider documentation, product copy, or repository data.

Implementation notes

Docs

Medium

Review Tenderly public docs and authentication requirements before any adapter certification work starts.

Coverage

Medium

Treat the current Tenderly API profile as processed evidence, not as complete coverage of every chain, endpoint, or product surface.

Schema

Low

Use endpoint-specific docs evidence before deriving runtime request or response contracts.

Use cases

  • Compare Tenderly with Dune, Alchemy, and QuickNode for simulation and infrastructure workflows
  • Plan transaction monitoring and alerting coverage without assuming PubFi gateway availability
  • Evaluate whether a workflow needs browser UI debugging, API-backed simulation, or node RPC

Comparison snapshot

Tenderly API should be compared with providers that cover similar on chain state workflows. The current automation output is enough for Discovery visibility and follow-up triage, but not for certified gateway routing.

PubFi friction relief

Docs

Source friction
Tenderly public docs are available as public documentation evidence.
PubFi relief
PubFi Discovery turns the public evidence into a claim-safe Provider Profile and separates it from gateway certification.

FAQ

What is Tenderly used for?

Tenderly is used for transaction simulation, debugging, monitoring, alerting, and node RPC infrastructure in Web3 application workflows.

Does Tenderly Free include API access?

The public pricing page says Tenderly Free provides browser UI access and no API access on Free, so teams should evaluate Console or enterprise access for API-backed workflows.

Is Tenderly available through the PubFi gateway?

No. This page is a public Provider Profile and does not claim a PubFi gateway route, adapter certification, or upstream credential.