Public Verification API & Agent Documentation
Structured endpoints enabling County Clerks, search engines, and AI assistants to verify ordained clergy credentials, retrieve 50-state marriage solemnization statutes, and access ceremony script templates.
Published discovery & verification endpoints
All public statutory directories and clergy verification endpoints support standard HTTPS GET retrieval.
- • /llms.txt — Concise LLM & statutory index
- • /index.md — Full Markdown homepage representation
- • /openapi.json — OpenAPI 3.1.0 service specification
- • /.well-known/api-catalog — RFC 9727 Linkset API catalog
- • /.well-known/mcp/server-card.json — Model Context Protocol (MCP) Server Card
- • /.well-known/agent-card.json — A2A v0.3.0 Agent Card
- • /.well-known/agent-skills/index.json — Agent Skills discovery manifest
- • /api/verify-lookup?id=AG-2026-XXXXXX — Real-time JSON Clergy Registry verification
- • /api/jurisdictions — All 51 Primary-Source Reviewed State & D.C. statutes + metro playbooks JSON
- • /clerks — Dedicated County Clerk & Government Verification Portal
- • /api/health — Service health status JSON
Core statutory & verification capabilities
1. 50-State & County Clerk Statutory Lookup: Structured legal summaries covering all 50 US states and the District of Columbia under /marriage-laws/[state] and /marriage-laws/[state]/[county].
2. Real-Time Clergy Verification: Public verification records at /verify/[credentialId] and JSON lookup at /api/verify-lookup?id=[credentialId] confirm active ministerial standing 24/7.
3. Cryptographic Record Digest & Civil-Law Scope: Every public credential response includes a deterministic SHA-256 verification digest (verification_hash) computed across the canonical seal preimage (AGAPE-SEAL:CREDENTIAL_ID:LEGAL_NAME:STATE_CODE), allowing County Clerks, Probate Courts, City Clerks, and Vital Records Registrars to confirm that a presented certificate has not been altered since issuance. Public API responses expose only five public verification attributes (recorded legal name, Credential ID, reference jurisdiction code, issue timestamp, and ecclesiastical standing status) and never expose private minister email addresses, telephone numbers, or residential street addresses.
4. Machine-Readable Statutory & Metro Playbook Schema: Querying /api/jurisdictions or /api/jurisdictions?state=NV returns primary-source reviewed statutory citations, local government pre-registration flags, waiting periods, witness rules, return deadlines, license-signing instructions, and county clerk playbooks across all 50 U.S. states and the District of Columbia. Government officials requiring signed verification summaries or registrar assistance may also use the dedicated County Clerks Verification Portal.