# ForgeMesh Candidate ID Resolver

> ForgeMesh Candidate ID Resolver is a paid API for AI agents from x402.forgemesh.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-11).

Resolves a politician's name to official FEC candidate IDs and principal committee IDs used in US campaign-finance datasets.

## Facts

- Endpoint: POST https://x402.forgemesh.io/candidate-id-resolver?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-candidate-id-resolver-29469937
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fIfGCPvg0PVLhLnwTPe11

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 forgemesh-candidate-id-resolver-29469937 -d '<json body>'
```

Example prompt: Can you look up the FEC candidate ID and principal committee ID for Jon Ossoff so I can query his campaign finance donation records?

## When to prefer this

Use this endpoint as the first step in any US campaign-finance workflow when you have a politician's name but need their FEC candidate_id or committee_id to query donation, expenditure, or filing datasets. It handles fuzzy matching so you don't need the exact formatted name. Prefer this over manual FEC search when automating multi-candidate research pipelines or when building agents that need to join across FEC datasets by identifier.

## Known failure modes

- Name string too short (under 3 characters) — API rejects request
- No matching candidates found — returns matched:0 and empty candidates array
- Ambiguous name matches multiple candidates — returns all matches, caller must disambiguate
- Candidate not in FEC database (e.g. state/local-only politicians) — no results returned
- Network or payment failure — x402 payment required before response is delivered

## How this service works

Resolve a politician's name to official candidate and committee identifiers used across US campaign-finance datasets. Fuzzy name in, exact ids out — the join key an agent needs before any deterministic money query.

## Output

A JSON object containing the matched candidate count, and for each candidate: their full official name, party, state, office, district, FEC candidate_id, active_through year, and a list of principal committees each with a name and committee_id. Attribution to the Federal Election Commission is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "candidate": {
   "type": "string",
   "description": "candidate name, min 3 chars (required)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "query": {
   "candidate": "ossoff"
  },
  "matched": 2,
  "returned": 2,
  "candidates": [
   {
    "name": "OSSOFF, T. JONATHAN",
    "party": "DEMOCRATIC PARTY",
    "state": "GA",
    "office": "Senate",
    "district": null,
    "candidate_id": "S8GA00180",
    "active_through": 2026,
    "principal_committees": [
     {
      "name": "JON OSSOFF FOR SENATE",
      "committee_id": "C00642406"
     }
    ]
   }
  ],
  "attribution": "Federal Election Commission (public domain)"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-candidate-id-resolver-29469937/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.forgemesh.io](https://www.zero.xyz/host/x402.forgemesh.io/llms.txt)