# WHP Standing — Wheeler Hubbell Publishing Core EPT Verification

> WHP Standing — Wheeler Hubbell Publishing Core EPT Verification is a paid API for AI agents from standing-guard-service.lovable.app, paid per call via x402, $1/call, status unknown (last checked 2026-10-11).

Returns a machine-verifiable authority record asserting standing, scope, and bounds for a given HTTP request under the WHP EPT (Explicit Permission Token) framework.

## Facts

- Endpoint: POST https://standing-guard-service.lovable.app/v1/ept/core?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/whp-standing-wheeler-hubbell-publishing-core-ept-verification-87c6b7b5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BNvP5jqRluhJO9v-ur991

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 whp-standing-wheeler-hubbell-publishing-core-ept-verification-87c6b7b5 -d '<json body>'
```

Example prompt: Can you verify my agent's standing and authority bounds under the WHP EPT framework by submitting an HTTP JSON POST check to the core endpoint, so I get back a machine-readable EPT asset record?

## When to prefer this

Choose this endpoint when you need a machine-verifiable, cryptographically-grounded authority record under the WHP Explicit Permission Token framework specifically — particularly when downstream systems require a WHP-EPT-ASSET-v1 record as proof of standing. Prefer this over generic auth or permission APIs when operating within the Wheeler Hubbell Publishing authority framework or when the axiomatic schema compliance record is required for audit or compliance purposes.

## Known failure modes

- Missing required 'type' or 'bodyType' fields returns a validation error
- Non-JSON body type or non-POST method may be rejected as out-of-scope
- Payment failure or insufficient USDC balance (x402 protocol) prevents the call from being processed
- Malformed input object structure causes schema validation rejection
- Service unavailability on lovable.app hosting infrastructure may return 5xx errors

## How this service works

Machine-verifiable standing under explicit authority and bounds.

## Output

A JSON object containing an EPT asset record with the schema identifier 'ept.core-axiomatic-schema' and a typed record of 'WHP-EPT-ASSET-v1', confirming machine-verifiable standing and authority bounds for the submitted request.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "bodyType"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "asset": {
   "asset": "ept.core-axiomatic-schema"
  },
  "record": {
   "type": "WHP-EPT-ASSET-v1"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/whp-standing-wheeler-hubbell-publishing-core-ept-verification-87c6b7b5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from standing-guard-service.lovable.app](https://www.zero.xyz/host/standing-guard-service.lovable.app/llms.txt)