We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Terms of use
These terms cover the Jurisdictional website, API and MCP server (together, "the service"). By using the service, you agree to these terms.
Last updated 2026-11-17.
Who runs Jurisdictional
Jurisdictional is made and run by Civic Studio. "We" on this page means Civic Studio.
The data and the service
The data is open. It is published under the Open Database License (ODbL) 1.0, with each record's contents under the Database Contents License (DbCL) 1.0. The data license page explains what that allows, how to credit the data, and how to get a commercial license for use without share-alike.
The service is how we deliver that data: our website, API, MCP server, servers and bandwidth. These terms govern how you use the service. They don't narrow what the data license allows you to do with data you have lawfully obtained.
Fair use of the service
Anyone may read the website, and the API and MCP read tools work without an account, within the shared anonymous limit. When you use the service, you agree to:
- stay within the rate limits for your key or, without a key, the shared anonymous limit;
- not get around those limits, for example with many keys, accounts, IP addresses or proxies;
- not disrupt the service, probe it for weaknesses, or reach data you aren't permitted to see;
- not impersonate a public official, a government or another person;
- not use the service to harass, threaten or target anyone;
- not resell or redistribute access to the service itself, for example by sharing a key or proxying the API for others, without a written agreement with us.
Automated access, crawlers and AI agents
Programs are welcome, including search engines, AI assistants and agents. Reading a page now and then, the way a person or an assistant answering a question would, needs nothing more than following our robots.txt.
Access at scale goes through the API or MCP server with your own key, not through the website. That includes crawling many pages, building a dataset, keeping a copy of the directory current, and running an agent or service for other people. It needs a paid plan, or a written agreement for bulk data, above the free limits. Identify your program honestly in its user agent.
We may slow, challenge, block or charge for automated access that doesn't follow this section, including with an HTTP 402 Payment Required response that points to our plans.
Paid plans
Paid plans raise your keys' limits and are listed on the pricing page . Payments are processed by Stripe.
- Plans are billed in advance each month and renew until you cancel.
- You can cancel at any time; your plan stays active until the end of the period you paid for.
- Payments are not refunded for partial periods, except where the law requires a refund.
- If a payment fails and isn't resolved, your keys return to the free limits.
- We may change prices with at least 30 days' notice to the email on your account.
- Taxes are added where they apply.
Contributions
Contributions come from public sources. Each one names the page or document it came from. Please contribute only what you have read in a public source, accurately, and only what you have the right to share.
By contributing, you agree that what you contribute is published as part of the database under the ODbL 1.0, with each record's contents under the DbCL 1.0. We may review, edit, decline or remove any contribution.
Accounts, keys and sign-in
You can create an account with your email address or sign in with GitHub. Apps such as Claude Code and the jurisdictional CLI sign in through your browser and receive a token that acts for your account. You are responsible for what is done with your account, keys and tokens. Keep them private, and revoke any you no longer use in Settings .
We may limit, suspend or close an account or key that breaks these terms or puts the service at risk. Where we can, we'll tell you why and give you a chance to sort it out.
Request logs
We log each request to the API and MCP server with the account and key that made it, to run the service, enforce limits and stop abuse. Each request is kept for 90 days, then deleted; daily totals are kept longer. The privacy page has the details.
No warranty, and limits of liability
We work to keep the data accurate and the service available, and we provide both as is and as available, without warranty of any kind. Government structures and officeholders change, so check an official source before you rely on a record for a decision that matters.
To the extent the law allows, Civic Studio is not liable for any indirect or consequential loss, or for lost profits or data, that comes from using the service or the data. Our total liability for any claim is limited to what you paid us in the 12 months before it arose, or $100 if you paid nothing.
If your use of the service breaks these terms or the law and someone makes a claim against us because of it, you agree to cover our reasonable costs of that claim.
Changes to these terms
We may update these terms as the service grows. The current version is always on this page, with its date. For a change that affects paid plans, we'll email account holders at least 30 days ahead. Continuing to use the service after a change means you accept it.
Questions, higher limits and partnerships
If a limit gets in the way of what you're building, or you'd like bulk data, a commercial license or a partnership, write to us. We'd rather find an arrangement that works than have anyone work around the rules. Newsrooms, nonprofits, researchers and governments are especially welcome to ask. Reach us at support@jurisdictional.org.