# Forest Gas Station – Service Component Status

> Forest Gas Station – Service Component Status is a paid API for AI agents from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-01).

Resolves the live operational state of a named service component by probing a given status URL.

## Facts

- Endpoint: POST https://http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/service/component-status?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forest-gas-station-service-component-status-e15deac8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xCTm0kQ15CH7MVFmxQkxU

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 forest-gas-station-service-component-status-e15deac8 -d '<json body>'
```

Example prompt: What is the current live status of the 'payment-processor' component? Check it at https://status.example.com/api and tell me if it's healthy or degraded.

## When to prefer this

Use this endpoint when you need a real-time, on-demand probe of a specific named service component's live state, especially when you have a direct status URL to interrogate. It is best suited for point-in-time health checks, pre-deployment gates, or incident triage where you know the component name and its status endpoint. Prefer this over general uptime monitoring tools when the component is identified by name and a custom status URL is available.

## Known failure modes

- Component name not found or unrecognized — status may return unknown or null state
- Provided status_url is unreachable or returns non-2xx — probe fails with network/timeout error
- Status URL returns malformed or unparseable response — component state cannot be resolved
- Component name exceeds 256 characters or is empty — validation error returned
- Status endpoint requires authentication that is not supplied — probe blocked with 401/403

## How this service works

Resolve the live state of a named service component. Base mainnet USDC

## Output

Returns the live operational state of the specified service component — typically indicating whether it is up, degraded, or down, as resolved from the provided status URL at the time of the call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "component": {
   "type": "string",
   "maxLength": 256,
   "minLength": 1,
   "description": "Public component value used to scope this lookup."
  },
  "status_url": {
   "type": "string",
   "description": "Public status url value used to scope this lookup."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forest-gas-station-service-component-status-e15deac8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run](https://www.zero.xyz/host/http--forest-gas-station-mainnet--lcjl27p8lmjs.code.run/llms.txt)