# Pathmint Proven Path Exchange — Compile Endpoint

> Pathmint Proven Path Exchange — Compile Endpoint is a paid API for AI agents from pathmint.edge.report, paid per call via x402, $0.55/call, status unknown (last checked 2026-09-14).

Compiles a sealed, bonded procedural path for an x402 merchant wallet by analyzing payment history to distinguish genuine outside revenue from self-seeded transactions.

## Facts

- Endpoint: POST https://pathmint.edge.report/v1/paths/x402-merchant-truth/compile
- Price: $0.55/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pathmint-proven-path-exchange-compile-endpoint-46229193
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T_scOC1N5kMdkr6dlkEHx

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 pathmint-proven-path-exchange-compile-endpoint-46229193 -d '<json body>'
```

Example prompt: Compile a proven path for my x402 merchant wallet 0xAbC123...def, excluding my self-seed wallets 0xSeed1 and 0xSeed2, and look back over the last 14 days to show me how much genuine outside revenue I've received.

## When to prefer this

Choose this endpoint when you need a cryptographically bonded, auditable summary of an x402 merchant wallet's genuine revenue on Base — specifically when you need to separate real customer payments from self-seeded or test transactions. It is preferable over raw blockchain explorers when you want a pre-compiled, structured path object rather than raw transaction data, and over generic analytics when you need x402-specific procedural verification.

## Known failure modes

- Missing or invalid payTo wallet address returns a validation error
- lookbackDays exceeding 30 is rejected with a parameter out-of-range error
- Unrecognized wallet address format (non-0x) causes schema validation failure
- Insufficient payment history for the requested window may return zero-value metrics
- Payment failure or x402 protocol error if USDC balance is insufficient

## How this service works

Proven Path Exchange — compile sealed procedures when the savings vs the fee are checkable. Primary: verify-before-pay clearance of an x402 payTo.

## Output

Returns a JSON object containing the compiled path ID, product name, total USD received from genuine outside payers, total USD identified as self-seeded, and the count of unique outside payers over the specified lookback window.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payTo": {
   "type": "string",
   "description": "0x payTo wallet receiving USDC on Base"
  },
  "seedWallets": {
   "type": "array",
   "description": "Optional self-seed wallets to exclude"
  },
  "lookbackDays": {
   "type": "number",
   "description": "Days of history to scan (default 7, max 30)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "path_id": "x402-merchant-truth",
  "product": "pathmint-compile",
  "outside_usd": 0.018,
  "self_seed_usd": 0.057,
  "unique_outside": 7
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pathmint-proven-path-exchange-compile-endpoint-46229193/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pathmint.edge.report](https://www.zero.xyz/host/pathmint.edge.report/llms.txt)