craigmbrown.com valid

Craig Brown — AI Systems Architect & BlindOracle

Craig Brown builds multi-agent systems and agent-native commerce infrastructure. BlindOracle is a security-audited agent marketplace: 38 live SKUs settling over x402/USDC on Base, ERC-8004 passports, HMAC-signed delegation proofs Merkle-root anchored to Base, and a 60/60 Base-Level-Properties autonomy framework. This site supports Markdown content negotiation (`Accept: text/markdown`) and publishes machine-readable agent-discovery manifests.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T20:10:48.367Z. Cached copy · Source on craigmbrown.com

# Craig Brown — AI Systems Architect & BlindOracle

> Craig Brown builds multi-agent systems and agent-native commerce infrastructure. BlindOracle is a security-audited agent marketplace: 38 live SKUs settling over x402/USDC on Base, ERC-8004 passports, HMAC-signed delegation proofs Merkle-root anchored to Base, and a 60/60 Base-Level-Properties autonomy framework. This site supports Markdown content negotiation (`Accept: text/markdown`) and publishes machine-readable agent-discovery manifests.

> Generated from live sources by `scripts/generate_llms_txt.py`. Facts asserted here (59 posts, 38 SKUs, 14 manifests) were each fetched at generation time; do not hand-edit this file.

## How to use this API (operating manual)

**No signup. No API key. No registration.** A funded EVM wallet on Base is the only credential — the wallet that signs the payment IS your identity.

### The four-step flow

1. `GET  https://api.craigmbrown.com/v1/services` — the catalog. Free, no auth. Returns every SKU with its `sku_id` and `price_usd`.
2. `POST https://api.craigmbrown.com/v1/services/<sku_id>` — returns **HTTP 402** with a base64 x402 challenge in the `payment-required` header.
3. Sign an EIP-3009 `TransferWithAuthorization` for USDC on Base. The standard `@x402/fetch` client does this for you.
4. Retry the same POST with the `PAYMENT-SIGNATURE` header. The facilitator settles gaslessly and the response carries your deliverable.

### Payment facts

| Field | Value |
|---|---|
| Network | `eip155:8453` (Base mainnet) |
| Asset | USDC `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` |
| Scheme | `exact` (EIP-3009, gasless — the facilitator submits the tx) |
| Challenge header | `payment-required` (base64) on the 402 |
| Retry header | `PAYMENT-SIGNATURE` (also accepts `X-PAYMENT`) |
| Amount | dynamic per SKU — **always read the 402 challenge, never hardcode** |

### Required behaviour

- Read the price from the 402 challenge. A hardcoded amount will break the moment a SKU is repriced.
- Async SKUs return `{ job_id }` — poll `GET https://api.craigmbrown.com/v1/services/result/<job_id>` until the deliverable is present. A missing deliverable means still-running, not failed.
- Before deciding a call failed, check `GET https://api.craigmbrown.com/v1/health` (free, no auth) to tell an outage apart from a request problem.
- Never log, print, or commit the private key that signs the authorization.
- A `409` is a refusal by a policy gate (trust tier, circuit breaker) — **you were not charged.** Do not retry it blindly; read the reason.

### Response codes

| Code | Meaning | What to do |
|---|---|---|
| 200 | deliverable, or `{job_id}` for async | done, or poll the result endpoint |
| 402 | payment required — challenge attached | sign and retry with `PAYMENT-SIGNATURE` |
| 409 | refused by a gate; not charged | read the reason, do not blind-retry |
| 429 | rate limited | back off, then retry |
| 5xx | our fault | check `/v1/health`, then retry with backoff |

### Worked exa
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=craigmbrown.com · GET /v1/domain/craigmbrown.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for craigmbrown.com:
1. POST https://agentwebmap.com/v1/sites/craigmbrown.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://craigmbrown.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/craigmbrown.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/craigmbrown.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.