Provider capabilities

Provider Capabilities

Capabilities declare what a provider supports and its limits. Validated at boot time.

capabilities:
  unsupported_categories: [debug, trace]
  unsupported_methods: [eth_getLogs]
  limits:
    max_block_range: 10000
    max_block_age: 1000
    block_age_methods: [eth_call, eth_getBalance]
  error_rules:
    - code: 35
      category: capability_violation
    - message_contains: "timeout on the free tier"
      category: rate_limit

Field	Type	Description
`unsupported_categories`	list	Method categories this provider doesn’t support (e.g., `debug`, `trace`)
`unsupported_methods`	list	Specific methods this provider doesn’t support
`limits.max_block_range`	integer	Max block range for `eth_getLogs`
`limits.max_block_age`	integer	Max block age for state methods (pruned provider)
`limits.block_age_methods`	list	Methods subject to `max_block_age` limit
`error_rules`	list	Provider-specific error classification overrides (first match wins)

When capabilities is omitted, defaults to permissive (only local_only methods blocked, no limits). These declarations constrain routing; they are not a proof of universal upstream compatibility. Test representative successful requests and known failure cases before relying on a provider-specific rule. Use the narrowest reliable match. Provider APIs, plans, and error messages can change. Discovery produces configuration for review. RPC Core does not promise unsupervised adaptation of every method, parameter, or historical limit. Changes to YAML require a successful reload on each running node. See Profiles.

Get Started

Core Concepts

Configuration

Deployment

Observability

Advanced

Provider capabilities

Provider Capabilities

​Provider Capabilities

Provider Capabilities