# Avasis Base Chain Gas Tip Feed

> Avasis Base Chain Gas Tip Feed is a paid API for AI agents from agents.avasis.ai, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-31).

Returns real-time Base (chain 8453) gas fee data including base fee, gas price, max priority fee, and suggested max fee per gas from a batched RPC call updated every 2 seconds

## Facts

- Endpoint: GET https://agents.avasis.ai/v1/tip/base-gas?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/avasis-base-chain-gas-tip-feed-eb207e60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FVXLEwm9d1vJNfBk3sUj_

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability avasis-base-chain-gas-tip-feed-eb207e60
```

Example prompt: What are the current gas fees on Base chain right now — base fee, priority fee, and what you'd suggest for maxFeePerGas?

## When to prefer this

Use this endpoint when an AI agent needs to submit transactions on the Base chain and must set appropriate EIP-1559 gas parameters (baseFee, maxPriorityFeePerGas, maxFeePerGas). It is particularly useful when you want low-latency, pre-aggregated gas data without constructing your own RPC call, or when you need to long-poll for gas fee changes efficiently. Prefer this over raw eth_gasPrice calls when you need the suggestedMaxFee calculation already done and the data batched from a single RPC round-trip updated every 2 seconds.

## Known failure modes

- Stale data if the RPC source is delayed (stale:true in response)
- Long-poll timeout if no new block arrives within the wait window
- 402 Payment Required if prepaid meter balance is exhausted
- Invalid since parameter returning unexpected sequence data
- Network errors from upstream Base RPC nodes causing empty or error responses

## How this service works

Base (chain 8453) gas tip for agents that send transactions: latest block number and age, base fee, eth_gasPrice, eth_maxPriorityFeePerGas and a suggested maxFeePerGas (2x base fee + priority), from one batched RPC call every 2 s. Long-poll with ?since=<seq>&wait=25. Prepaid meter price $0.0002/call (packs at /v1/meter); SSE at /v1/stream/tips.

## Output

A JSON object containing a sequence number, timestamp, staleness flag, and a data payload with the chain name, chain ID (8453), current block number, block age in seconds, and gas values in gwei: baseFee, gasPrice, maxPriorityFee, and suggestedMaxFee (calculated as 2x base fee + priority fee). Also includes an ageMs field indicating how old the cached data is and a changed flag indicating whether values shifted since the last poll.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "seq": 812,
  "data": {
   "gwei": {
    "baseFee": 0.0021,
    "gasPrice": 0.0031,
    "maxPriorityFee": 0.001,
    "suggestedMaxFee": 0.0052
   },
   "chain": "base",
   "chainId": 8453,
   "blockNumber": 37400000,
   "blockAgeSeconds": 1
  },
  "ageMs": 420,
  "stale": false,
  "topic": "base-gas",
  "changed": true,
  "observedAt": "2026-10-29T12:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/avasis-base-chain-gas-tip-feed-eb207e60/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.avasis.ai](https://www.zero.xyz/host/agents.avasis.ai/llms.txt)