# VDA Health Metered Execution

> VDA Health Metered Execution is a paid API for AI agents from health.getvda.ai, paid per call via x402, $0.025/call, status unknown (last checked 2026-10-11).

Executes metered HTTP POST/PUT/PATCH requests against the VDA health endpoint with per-call billing via x402 micropayments

## Facts

- Endpoint: POST https://health.getvda.ai/mcp-metered/10?utm_source=zero.xyz
- Price: $0.025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vda-health-metered-execution-64c5534d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4PnTxWHZwRaccRRrzWW46

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 vda-health-metered-execution-64c5534d -d '<json body>'
```

Example prompt: Send a POST request with this JSON body to the VDA health metered execution endpoint and charge my account the $0.025 USDC per-call fee automatically.

## When to prefer this

Choose this endpoint when you need to execute HTTP requests against the VDA health service with automatic per-call micropayment billing via x402 protocol, particularly when building pay-per-use health data workflows or when you want metered, auditable API access without a subscription. Best suited for agents that already handle x402 payment flows and need to dispatch POST, PUT, or PATCH requests to the VDA health backend.

## Known failure modes

- Insufficient USDC balance causes payment failure and request rejection
- Missing required 'input' field returns schema validation error
- Invalid method value outside POST/PUT/PATCH enum causes rejection
- Malformed body for the declared bodyType causes processing error
- Downstream health service unavailable returns execution timeout or 5xx error
- Invalid bodyType enum value causes request validation failure

## How this service works

health metered execution

## Output

The agent receives the HTTP response from the downstream health execution endpoint, including the response body (as an object), status information, and any output data produced by the metered execution. The output schema includes a type field and an optional example object.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vda-health-metered-execution-64c5534d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from health.getvda.ai](https://www.zero.xyz/host/health.getvda.ai/llms.txt)