Legalcode

Primary-source legal research

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Legal research grounded in primary sources. Legalcode gives ChatGPT direct access to statutes, case law, regulatory guidance, agreements, legislative history, and patents across more than 40 jurisdictions — tens of millions of indexed documents from official publishers, court databases, and regulatory portals — with human-readable citations and links to official materials, so you can verify conclusions against the original text instead of taking citations on faith. Search goes far beyond full text. Sources are indexed with deep legal metadata, so you can filter by court, judge, counsel, party, outcome, cited legal basis, act type, issuing agency, or date — find the version of a law in force on a specific date, or jump straight to a known instrument by its official number or citation. Fetch retrieves the text itself: a complete act or judgment, or one targeted provision — a single article or section — with the metadata to cite it. Analyze turns the whole corpus into answers no single document holds: group decisions on a topic by year, cross-tabulate outcomes by court, chart a trend over time, or surface the legal bases courts cite most. Trace follows indexed relationships: which decisions apply a law, what a judgment cites, which national law implements an international instrument, and the legislative history behind a provision. Legalcode receives only your research queries — processed, never stored. Your documents stay in ChatGPT. Coverage varies by jurisdiction and source.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Unknown
Access: Account required
First tracked: 2026-09-03
Tool count: 5
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Legalcode has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

5 tools agents can invoke

Analyze supported corpora with counts, rates, averages, groups, matrices, trends, and actor statistics. Read Discover source_profile first: analyticsStatus and analyticsCapabilities are executable truth for the jurisdiction and source. Use court_case for court-only analysis and case for the broad decision rollup. Analysis may require q or a positive narrowing filter for expensive case aggregates, actor analysis, and high-cardinality matrices. q and a body-text filter target the same text, so provide one. Use measure document_count rather than count. Request sourceRef samples only when the profile explicitly allows them; use Search with matching filters for representative documents otherwise.
legalcode_analyze
Discover the exact Legalcode search contract before querying: source-owning jurisdictions, agreement-party scopes, named sources and scoped sourceCode values, supported fields, bounded facets, prefix-constrained facet values, analytics and relationship readiness, query syntax, costs, and examples. Use mode:"jurisdictions" for corpus owners; mode:"agreement_scopes" for treaty/agreement coverage; mode:"source_profile" with jurisdiction and sourceType for fields and capabilities; mode:"facets" or "facet_values" for stored filter values; and mode:"help" for workflows. Treat case as the broad decision rollup, court_case as confidently classified courts, and agency_decision as administrative, regulatory, or tribunal decisions. Never guess sourceCode or enum values.
legalcode_discover
Inspect one document using a sourceRef copied exactly from Search or Trace. mode:"metadata" returns document context and law-version status. mode:"excerpt" uses q or sectionRef for a targeted passage; supported structured references include Icelandic articles, Irish sections, EU articles, and Icelandic bill commentary sections. Prefer a returned downloadUrl for complete-document retrieval. mode:"full" is a cursor-paginated fallback only when a download is absent or unavailable; follow nextCursor until truncated is false. An official publisher URL is provenance metadata, not a text-retrieval instruction.
legalcode_fetch
Search ranked primary-source candidates and snippets. Choose one jurisdiction and one or more discovered sourceTypes: law (including regulations, narrowed by actType), case (broad decision rollup), court_case, agency_decision, guidance, agreement, pre_law, or patent. Prefer explicit identifier filters such as lawKey, CELEX, ELI, citation, or sourceCode for known instruments. q remains free text and never creates structured filters. Use quoted phrases or flat AND/OR; do not send raw SQL, fielded backend syntax, wildcards, or a language filter. Results include sourceRef and may include a signed downloadUrl; use Fetch for metadata or targeted excerpts and follow response nextAction guidance.
legalcode_search
Trace deterministic indexed relationships rather than ranked text matches. Supported families include cases_for_law, laws_for_case, cited_cases, citing_cases, pre_law_for_law, related_pre_law_flows, eea_incorporation_for_law, implementing_laws_for_eu_law, and eu_law_for_implementing_law. Start from a sourceRef or an exact law, case, citation, or legal-basis key. Short number/year keys require an explicit jurisdiction. Relationship availability and resolution coverage vary by source; inspect Discover source_profile/help before relying on an edge family. After a pre-law trace returns a flow, use Search resultLevel:"document" with its flowKey to enumerate attached documents.
legalcode_trace

Legalcode FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.