# Lotus Network Gas Decision Journal

> Lotus Network Gas Decision Journal is a paid API for AI agents from lotusnetworkapi.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Records an agent's gas decision (execute or wait) against a current gas forecast snapshot, returning a tamper-evident decision_id and the block at which the outcome can be verified.

## Facts

- Endpoint: POST https://lotusnetworkapi.com/api/v1/gas/decision
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lotus-network-gas-decision-journal-75e13258
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7D7-gsutC7A24RHj_KqWL

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 lotus-network-gas-decision-journal-75e13258 -d '<json body>'
```

Example prompt: Log my gas decision to execute now against the current Base L2 gas snapshot — my max fee is 12 Gwei, my horizon is 10 minutes, and note that this is for a DeFi swap so I can prove later what conditions I acted on.

## When to prefer this

Use this endpoint when an AI agent needs a tamper-evident, auditable record of a gas-related decision tied to a specific on-chain snapshot — particularly for compliance, post-hoc verification, or proving rational behavior. Prefer this over simple logging when proof-of-knowledge at a specific block is required.

## Known failure modes

- Invalid stance value (not 'execute' or 'wait') returns a 422 validation error
- Missing required fields returns 400 bad request
- Payment not included or incorrect USDC amount returns 402 Payment Required
- Service unavailable if underlying gas snapshot feed is down
- Duplicate rapid submissions may create multiple independent journal entries — not idempotent

## How this service works

Records an agent decision (execute now, or wait) against a fresh forecast snapshot and returns a decision_id plus the block at which the outcome becomes checkable. Nothing is predicted here beyond the snapshot: this is a tamper-evident journal entry so the agent can later prove what it knew and what it chose.

## Output

Returns a decision_id uniquely identifying this journal entry, plus the block number at which the outcome becomes checkable, allowing the agent to later verify and prove what gas conditions it observed and what action it committed to.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "note": {
   "type": "string"
  },
  "stance": {
   "enum": [
    "execute",
    "wait"
   ],
   "type": "string"
  },
  "maxFeeGwei": {
   "type": "number"
  },
  "horizonMinutes": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "stance": "wait",
  "success": true,
  "auditUrl": "https://lotusnetworkapi.com/api/v1/gas/audit/7c1f9a2b4d6e8f0a1b2c3d4e5f607182",
  "snapshot": {
   "lowGwei": 0.0106,
   "highGwei": 0.0182,
   "baseFeeGwei": 0.0142
  },
  "decisionId": "7c1f9a2b4d6e8f0a1b2c3d4e5f607182",
  "recordedAt": "2026-07-30T04:12:00.000Z",
  "auditableAt": "2026-07-30T04:27:00.000Z",
  "targetBlock": 24881453
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lotus-network-gas-decision-journal-75e13258/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lotusnetworkapi.com](https://www.zero.xyz/host/lotusnetworkapi.com/llms.txt)