API Health Check

Call an API endpoint and check the response status and schema.

Pay by wallet (x402) api-health-check

Example

Example answer
{
  "url": "https://example.com",
  "error": "fetch failed",
  "method": "GET",
  "is_healthy": false,
  "response_time_ms": 12
}

Inputs

FieldTypeRequiredWhat it is
urlstringYesAPI endpoint URL
bodyanyNo—
methodstringNo—
headersobjectNo—
expected_schemaobjectNo—
expected_statusintegerNo—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
is_healthybooleanAlways (present in every successful answer)
status_codeintegerAlways (present in every successful answer)
schema_validbooleanAlways (present in every successful answer)
response_bodyanyAlways (present in every successful answer)
response_time_msintegerAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "api-health-check",
    "inputs": {
      "url": "https://api.strale.io/health"
    },
    "max_price_cents": 5
  }'

Limitations

  • Business logic and data integrity are not checked

    Checks endpoint reachability and response status — cannot verify business logic correctness or data integrity

    What to do instead: Validate the expected response schema and test business rules separately.

  • API responses are limited to 4 MiB

    API response bodies above 4 MiB are refused during download rather than parsed.