# CAPI2 Momentum Foundry – Lead Qualification

> CAPI2 Momentum Foundry – Lead Qualification is a paid API for AI agents from capi2-foundry.vandurmedries.workers.dev, paid per call via x402, $0.007/call, status unknown (last checked 2026-10-11).

Scores and qualifies a sales lead based on company size, budget status, urgency, and intent signals, delivered after x402 micropayment settlement.

## Facts

- Endpoint: POST https://capi2-foundry.vandurmedries.workers.dev/v1/products/lead-qualification/run?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/capi2-momentum-foundry-lead-qualification-0505ed0e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_g7RQLXdoSVnD9tMQi-_lp

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 capi2-momentum-foundry-lead-qualification-0505ed0e -d '<json body>'
```

Example prompt: Qualify this lead for me: the company has 350 employees, they've confirmed they have budget, their urgency window is 14 days, and their intent signal score is 8 — tell me if they're a strong prospect.

## When to prefer this

Use this endpoint when you need a structured, verifiable lead qualification score computed from explicit CRM-style signals (headcount, budget, urgency, intent) and want a cryptographically receipted result via x402 micropayment. Prefer this over rule-based CRM filters when you need an external, auditable qualification pass with a delivery proof chain, or when integrating lead scoring into an autonomous agent workflow that already handles x402 payment flows.

## Known failure modes

- Missing required fields (employees, hasBudget, urgencyDays, intentSignals) may return a 400 or empty result
- Payment not settled via x402 protocol results in 402 Payment Required before processing begins
- Invalid data types (e.g. string instead of number for employees) may cause computation errors
- Workers.dev cold start may add occasional latency on first call
- Receipt signature mismatch may indicate tampering or delivery error

## How this service works

Paid agent utilities delivered after verified x402 settlement.

## Output

Returns a JSON object with a 'result' payload containing the lead qualification output, a creation timestamp, the product ID ('lead-qualification'), and a signed delivery receipt including the payer wallet address, receipt UUID, delivery timestamp, input and result SHA-256 hashes, atomic USDC amount paid (7000), and a signature hash for verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "employees": {
   "type": "number",
   "description": "Company headcount"
  },
  "hasBudget": {
   "type": "boolean"
  },
  "urgencyDays": {
   "type": "number"
  },
  "intentSignals": {
   "type": "number"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {},
  "createdAt": "2026-09-23T00:00:00.000Z",
  "productId": "lead-qualification",
  "deliveryReceipt": {
   "payer": "0x0000000000000000000000000000000000000000",
   "productId": "lead-qualification",
   "receiptId": "00000000-0000-4000-8000-000000000000",
   "deliveredAt": "2026-09-23T00:00:00.000Z",
   "inputSha256": "example-input-sha256",
   "amountAtomic": "7000",
   "resultSha256": "example-result-sha256",
   "signatureSha256": "example-signature-sha256"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/capi2-momentum-foundry-lead-qualification-0505ed0e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from capi2-foundry.vandurmedries.workers.dev](https://www.zero.xyz/host/capi2-foundry.vandurmedries.workers.dev/llms.txt)