# LedgerProof LAIN Confidence

> LedgerProof LAIN Confidence is a paid API for AI agents from ledgerproofhq.io, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Gathers and anchors independently verifiable public-record evidence about an entity, product, or firm to quantify confidence levels, returning a cryptographically anchored evidence receipt and evidence-graph node.

## Facts

- Endpoint: POST https://ledgerproofhq.io/api/lain/confidence
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ledgerproof-lain-confidence-00c0c087
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AzdxdneMtbtCQujQtV0yz

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 ledgerproof-lain-confidence-00c0c087 -d '<json body>'
```

Example prompt: Can you pull independently verifiable public-record evidence about Acme Robotics Inc. — I currently have 0.3 confidence in them and need to reach at least 0.8 before we proceed with the partnership?

## When to prefer this

Choose this endpoint when you need cryptographically anchored, independently verifiable evidence about a specific entity, product, or firm — particularly for due diligence, compliance, or trust-gating workflows where a permanent, auditable evidence trail is required. It is especially valuable when you have a current confidence score and a required confidence threshold, and need to close the gap with structured public-record evidence rather than unverified web search results.

## Known failure modes

- Subject entity not found in public records — insufficient evidence returned
- Payment settlement failure via x402 protocol — call not processed
- Invalid confidence range (values outside 0–1) — schema validation error
- Subject string too ambiguous — multiple entity matches with no disambiguation
- Anchoring service unavailable — receipt generation fails

## How this service works

LAIN confidence: independently verifiable evidence about the subject — <entity/product/firm>

## Output

Returns an outcome of 'settled' along with an anchored evidence receipt containing a content hash, sequence number, and a verify URL for independent verification, plus a permanent evidence-graph node backed by public-record evidence about the queried subject.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "subject": {
   "type": "string",
   "description": "entity, product or firm to gather evidence about"
  },
  "settlement": {
   "enum": [
    "x402"
   ],
   "type": "string"
  },
  "current_confidence": {
   "type": "number",
   "maximum": 1,
   "minimum": 0
  },
  "required_confidence": {
   "type": "number",
   "maximum": 1,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "outcome": "settled",
 "receipt": "anchored evidence receipt {content_hash,sequence,verify_url}",
 "evidence": "anchored public-record evidence + a permanent evidence-graph node"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ledgerproof-lain-confidence-00c0c087/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ledgerproofhq.io](https://www.zero.xyz/host/ledgerproofhq.io/llms.txt)