# Records for Agents: Contractor & Trade License Verification

> Records for Agents: Contractor & Trade License Verification is a paid API for AI agents from licenses.recordsforagents.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Verifies US contractor and trade licenses by name or license number across TX TDLR, FL DBPR, OR CCB, and CT eLicense databases with fuzzy matching and provenance metadata

## Facts

- Endpoint: GET https://licenses.recordsforagents.com/verify
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/records-for-agents-contractor-trade-license-verification-f570b78e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X269Ih-lbb8ClRawrYvRe

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 records-for-agents-contractor-trade-license-verification-f570b78e
```

Example prompt: Can you verify whether John Martinez holds a valid electrician license with Texas TDLR? Search by name and let me know his license status, expiration date, and whether there are any disciplinary orders on record.

## When to prefer this

Choose this endpoint when you need to verify contractor or trade licenses specifically in Texas (TDLR electricians and A/C contractors), Florida (DBPR construction), Oregon (CCB construction contractors), or Connecticut (eLicense professional credentials), and you need full provenance metadata, fuzzy name matching, and freshness timestamps. Prefer this over generic web search when you need structured, auditable license verification with record hashes. Note coverage limitations: status information varies by state, and some upstream sources exclude certain inactive license categories.

## Known failure modes

- No matching record found for the given name or license number — returns empty result set
- Fuzzy name match returns multiple candidates requiring disambiguation
- TX TDLR and OR CCB records lack a license-status column — expiration date is the only status proxy, which may mislead if the caller expects an explicit active/inactive flag
- FL DBPR upstream file excludes null-and-void, delinquent, and involuntarily-inactive licenses — absent records do not confirm non-licensure
- Stale data if source files have not been recently fetched — check as_of freshness field
- Input schema malformed or missing required query parameters returns an error

## How this service works

US contractor and trade license verification for AI agents: Texas TDLR electrician and A/C contractor/technician rosters, Florida DBPR construction licenses, Oregon CCB construction contractor licenses, Connecticut eLicense professional/occupational credentials, and TDLR disciplinary/administrative orders. Search by name, license number, state, or profession; verify a business or person against the roster with fuzzy name matching; look up board discipline history. Coverage is honest, not exhaustive: TDLR bulk files carry no license-status column (expiration date is the only status proxy we have, reported as such), DBPR's file excludes null-and-void/ delinquent/involuntarily-inactive licenses upstream, and Oregon CCB likewise has no status column (see docs/licensing.md); Connecticut eLicense DOES carry real status/active columns, reported verbatim. Every record carries full provenance (source, source URL, fetched-at, record hash) and every response includes as_of freshness — built for agent-driven verification and compliance workflows.

## Output

Returns matched license record(s) including licensee name, license number, profession/trade type, state, expiration date (used as status proxy for TX TDLR and OR CCB where no status column exists), verbatim active/status fields for CT eLicense and FL DBPR, source name, source URL, fetched-at timestamp, record hash, and an as_of freshness indicator. Fuzzy name matching is applied when searching by name. May include disciplinary/administrative order history where available.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/records-for-agents-contractor-trade-license-verification-f570b78e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from licenses.recordsforagents.com](https://www.zero.xyz/host/licenses.recordsforagents.com/llms.txt)