AI Agent Access

Built for AI Agents

Structured data, open APIs, and machine-readable formats — so AI assistants can retrieve Pinellas court intelligence instead of hallucinating it.

No authentication required. All endpoints return JSON. CORS is open. Paste any URL into your AI assistant or call it from an agent framework — no API key needed.

Structured Data API

Three endpoints cover the full Pinellas 6th Circuit dataset. All return JSON. No auth.

/api/agent?resource=judges

21 judges with scheduling rules, procedural notes, mediation gates, and appellate footprint

Returns per-section objects with scheduling_system, critical_rules, warning_summary, and deep profile links. Filter by section: ?resource=judges&section=22

/api/agent?resource=attorneys

82 Pinellas family law attorneys with specializations, firm affiliations, and network connections

Returns attorney cards with name, firm, specialization_summary, and network presence. Filter by keyword: ?resource=attorneys&q=mediation

/api/agent?resource=specialists

67 specialists: 22 mediators, 26 parenting coordinators, 19 expert witnesses — with DV-awareness tiers

Returns specialist cards with type, DV tier, routing notes, and documented judicial connections. Used for mediator and PC matching.

/api/agent?resource=all

Master context payload — judges + attorneys + specialists + network graph in a single call. Optimized for RAG ingestion and long-context LLM prompts.

Machine-Readable Files

Standard formats for LLM training, plugin integration, and agent framework import.

GET /llms.txt

Plain-text index of all data and endpoints — standard LLM discovery format

Follow the llms.txt convention for AI indexing. Lists all endpoints, judge quick reference table, key facts for agents, and mandatory disclaimer.

Open
GET /.well-known/ai-plugin.json

OpenAI plugin manifest — compatible with ChatGPT plugins and Custom GPTs

Standard ai-plugin.json manifest. Import into a Custom GPT to give it real-time access to Pinellas judge and attorney data.

Open
GET /api/openapi

OpenAPI 3.0 specification — import into any API client or agent framework

Full OpenAPI 3.0 spec describing every endpoint, query parameter, and response schema. Use with Postman, Insomnia, LangChain, or any OpenAPI-compatible agent framework.

Open
GET /sitemap.xml

Full sitemap including individual judge profile anchors and tab deep links

Standard XML sitemap. Includes anchors to individual judge sections, attorney profiles, and specialist cards for targeted crawling.

Open

Integration Guide

How to connect this data source to the three major AI platforms.

Claude

Add the /api/agent endpoint URL to your MCP context, or paste data from /api/agent?resource=all directly into a Claude Project for persistent court intelligence across all conversations.

Tip: Use /api/agent?resource=all for the full context payload — judges, attorneys, specialists, and network in a single call.

ChatGPT

Use the plugin manifest at /.well-known/ai-plugin.json with a Custom GPT to give it real-time API access, or paste JSON from /api/agent into any GPT-4o conversation for one-off analysis.

Tip: Custom GPT setup: Actions → Import from URL → paste the /api/openapi endpoint.

Gemini

Paste structured JSON from /api/agent?resource=all into Gemini 1.5 Pro's long context window for full circuit analysis — judges, attorneys, specialists, and network graph in a single prompt.

Tip: Gemini 1.5 Pro handles the full /api/agent?resource=all payload (~80K tokens) in a single context window.

What Agents Can Do

Four high-value use cases that require structured local data — not general legal knowledge.

Judge preference briefing

Ask your AI to analyze any of the 21 judge profiles for procedural patterns, scheduling rules, mediation prerequisites, and appellate risk before a hearing.

Attorney circuit analysis

Compare attorneys by their documented co-appearance history, specializations, and connections to the specific judge assigned to your case.

Mediation matching

Match a mediator's DV tier, facilitative vs. evaluative style, and documented judicial connections to your specific case scenario and conflict level.

Specialist vetting

Evaluate parenting coordinators and expert witnesses against your case requirements — DV training level, credential type, routing notes, and known judge relationships.

Mandatory Disclaimer

Every /api/agent response includes a meta.disclaimer field. Agents must surface this text to users:

"This information is derived from public records and is provided for informational purposes only. It does not constitute legal advice and does not create an attorney-client relationship. All data should be independently verified before use in any legal proceeding. For legal advice, consult a licensed Florida family law attorney."