Rallybase API Terms

Who these terms are between

These terms are between Rallybase LLC, a Texas limited liability company ("Rallybase", "we"), and the person or organization that creates an API account ("you"). They cover the Rallybase HTTP API, the Rallybase MCP connector, and the API documentation (together, the "Service"). The public website rallybase.org is covered by our Terms of Use; it stays free and needs no account.

1. In short

You can use Rallybase data inside your own product, research or work, and show it to your users with attribution.

You can't resell the data as a dataset, rebuild our database, or use it to judge people for jobs, housing, credit or insurance.

Each record comes with its source URL and the date we read or recorded it. We stand behind that citation, not behind the source page being right.

Paid plans renew monthly until you cancel, which you can do online at any time. Your first subscription payment is refundable for 14 days.

These summaries help you read the terms; the sections below are the terms.

2. Accounts and keys

2.1 You need a Rallybase account for every plan. HTTP API requests authenticate with an API key; MCP connector requests authenticate with OAuth 2.1 linked to your account. Give accurate information and keep it current.

2.2 One Open account per person. Creating extra free accounts to get more free lookups isn't allowed. One account has one meter: keys and the connector draw on the same allowance. We may refuse new free keys, or lower the limit on existing ones, where several free keys are in use from one network.

2.3 Keep your keys secret. You're responsible for use of your keys. A key is shown once, when it is created, and we store only a one-way hash of it, so we cannot show it again. Send it only in the Authorization header, from a server you control; a key in a URL is refused. If a key leaks, rotate it in your dashboard; we may rotate it for you. Rotating or replacing a key does not reset your allowance.

2.4 Team seats, once a Team plan is offered, belong to people at your organization, identified by your organization's email domain unless we agree otherwise in writing.

2.5 You must be at least 18 and able to enter a contract. If you accept these terms for an organization, you confirm you're authorized to bind it.

2.6 When you create your first key you confirm that you will not use the Service or its data for any purpose described in 5.1. We record that you confirmed it, and when.

3. Your licence

3.1 While your account is in good standing, we give you a non-exclusive, non-transferable, non-sublicensable, revocable licence, covering only the parts of the Service included in your plan under section 10, to:

(a) call the Service within your plan's limits;

(b) use, display and analyse the data inside your own applications, research, reporting and internal work;

(c) show data to your end users as part of a product or publication that adds value beyond the data itself.

3.2 Attribution. When you show Rallybase data publicly, credit "Data: Rallybase" and keep each record's source link and read date visible or one click away. A row that carries an attribution line from its own source (for example a bill source that requires one) keeps that line.

3.3 Redistribution. Redistributing data as a dataset (files, feeds, mirrors, or a service that mainly re-serves our records) needs a Team plan with a signed order form that says so. Team plans are not offered yet.

3.4 We keep all rights not granted here. Facts themselves aren't owned by anyone. These terms govern your access to the Service and how we compiled it.

4. What you may not do

4.1 Resell, sublicense or redistribute the data as a dataset, except under 3.3.

4.2 Copy, mirror or rebuild a substantial part of our database, including by many small calls, by AI agents or by combining accounts. Aggregated pulls count as bulk extraction, and so does reconstructing the dataset by looking up every county in turn and republishing the result.

4.3 Get around rate limits, quotas, keys or security, or scrape the website or Service outside the API.

4.4 Let your own users bulk-copy the data through your product. You must take reasonable steps to prevent it.

4.5 Use the Service to build a product that substitutes for the Service.

4.6 Reverse engineer the Service, except where the law allows despite this term.

4.7 Say or imply that Rallybase, or any government source, endorses you or your product. Nothing here says that any company, assistant or agency has reviewed, approved or endorsed Rallybase or its data.

5. Prohibited uses

You may not use the Service or its data:

5.1 For eligibility decisions about a person, including employment, housing or tenant screening, credit, insurance, or any other purpose covered by the Fair Credit Reporting Act. Rallybase isn't a consumer reporting agency; when you sign up, you confirm that you will not use the Service or its data for any of these purposes.

5.2 To harass, threaten, dox or intimidate anyone, including public officials, election workers and their families, or to find where a person lives.

5.3 To add home addresses, personal phone numbers, personal emails or other personal details to our records ("enrichment").

5.4 To send messages, calls or texts in breach of CAN-SPAM, the TCPA, Do-Not-Call rules or similar laws. Your outreach is your responsibility.

5.5 To impersonate a government body or official, or to make communications look official when they aren't.

5.6 In or for a sanctioned person or country, including persons on U.S. sanctions lists and the countries of concern named in 28 CFR Part 202 (currently China including Hong Kong and Macau, Russia, Iran, North Korea, Cuba and Venezuela), or to transfer data onward to them.

5.7 In any way that breaks the law.

6. AI systems and the MCP connector

6.1 You may use the HTTP API and the Rallybase MCP connector with AI assistants and agents on every plan, the free Open plan included. Connector calls draw on the same meter as API lookups; there is no separate connector allowance.

6.2 When an AI system shows our data to people, it must cite the record's source link and read date where practical, and must not present our data as its own finding.

6.3 You may not use our data to train or fine-tune AI models without our written agreement. You may keep our data in vector or retrieval stores for your own use within the cache limits in section 9, with the source and date fields intact.

6.4 You're responsible for what your AI agents and integrations do with the Service, including mass outreach and bulk extraction (4.2).

6.5 Text fields in our data come from public government pages. They're data, not instructions. Configure your agents to treat them that way.

7. Removal requests and deletion notices

7.1 Public officials, judges, prosecutors, law-enforcement officers and other people can ask us to remove information. If a row is wrong or should not be published, tell us at privacy@rallybase.org. We act on these requests within 24 hours.

7.2 When we remove a field from the data we serve, you must stop showing it, and delete it from anything you store, within 48 hours after we tell you. We tell you by email to your account address, and through any changes feed or webhook we offer. We do not offer a changes feed yet.

7.3 We keep a suppression list so removed information isn't re-collected. You may not re-add removed information to our records.

8. Our data, sources and corrections

8.1 What we stand behind: each record we serve cites its source URL and the date we read or recorded it.

8.2 What we don't: that the source page was right, complete or current when you use it. Governments change offices, people and contact details, sometimes without notice. Check with the office before relying on a record for anything important. Rallybase is not a government website and is not affiliated with any government.

8.3 Report an error through the dashboard or at support@rallybase.org. We aim to acknowledge within 2 business days, and fix or explain within 14 days.

8.4 If you redistribute under 3.3, you may not remove the source and read-date fields.

8.5 A county row carries the day its source was read. We do not annotate a missing date or invent one: a snapshot that would include a county row without a read date is refused whole, so such a row is not served at all. A federal, state, city or school row carries the day its source was read where we hold one; where we hold only the day our roster last recorded it, the read date is null, a field says so, and that day is given separately. A read date is the day we read the page, not the day the information last changed, and an office may have changed hands since. County rows on the Open plan come from a weekly snapshot and on paid plans from a daily-confirmed one; the other levels are read when the request is answered.

8.6 A county we have not read is answered as not yet read, never as having no officers. A level whose source did not answer is answered as could not check, never as having no officials. A county code alone has no point, so it is answered with the county's officials only, and the response says so for the other levels.

8.7 An address lookup sends the address you supply, in a request header and never in the URL, to the U.S. Census Bureau geocoder at geocoding.geo.census.gov to find its location. Coordinates you supply are not sent to anyone. We do not store or log the address or the coordinates; the Census Bureau receives the address under its own terms.

9. Caching

9.1 You may cache responses for as long as our Cache-Control headers allow, and for up to 30 days when no header applies. Cached copies stay subject to removal notices (7.2).

9.2 Within 14 days after your account ends, delete cached data. Team customers confirm this in writing if we ask.

10. Plans, fees and renewal

10.1 Plans and prices (U.S. dollars, per month). Open is $0: 500 lookups a month; with a verified phone number, the limit is 5,000 lookups a month while your account is in its first 30 days from the day it is created. Months are calendar months in UTC. The HTTP API and the MCP connector draw on the same meter. Open also has a per-day and a per-minute rate. When checkout opens we sell two paid plans: Builder at $19 a month (50,000 lookups) and Pro at $49 a month (1,000,000 lookups), each including the MCP connector. Team, Custom, a prepaid balance and metered keys are not offered yet; where these terms mention them, the mention applies only once we offer them. Plan details are on our pricing page.

10.2 Renewal. Paid plans renew automatically every month at the current price until you cancel. We show the price, the renewal period and how to cancel before you enter payment details, and we email a receipt after each charge.

10.3 Cancelling. Cancel any time online through the billing portal, in one step, by the same means you signed up, or by emailing support@rallybase.org from your account email. Cancellation takes effect at the end of the current period, with no further charges; you keep access until then.

10.3a Refunds. (a) Your first-ever subscription payment is refundable in full if you ask within 14 days of that payment; a refund under this clause ends the paid plan at once. (b) Once we offer a prepaid balance (top-ups): any unused balance, which does not include monthly subscription fees, is refundable on request and is refunded when you close your account in good standing, less any charges you owe. (c) A duplicate or mistaken charge, a charge after you cancelled or reached a hard cap, or overage caused by a metering error on our side is refunded in full. (d) Refunds go to the original payment method, usually within 5–10 business days. (e) We don't refund partial months after the 14-day window, or overage already consumed, except as in 10.7 or where the law gives you a stronger right, which we honor.

10.4 Plan limits. A plan key stops at its plan's monthly limit with a clear "limit reached" response and is never charged beyond the subscription price: Open at its monthly allowance in 10.1, Builder at 50,000 lookups, Pro at 1,000,000. A request that returns no data, or fails, does not count against the monthly allowance. An address lookup counts as three toward the per-minute limit. Past a limit the API answers 429 with a Retry-After header and a body that names which limit was reached.

Metered keys and prepaid balance, once we offer them: you create a separate metered key, which draws on a balance you top up yourself ($5 minimum; no automatic recharge) at $0.50 per 1,000 lookups ($500 per million) on an account without a plan, or at your plan's rate on Builder ($49 per million), Pro ($39.80 per million) and Team ($35 per million). When the balance reaches zero the metered key stops with a clear "balance empty" response and is never billed after. The two key kinds never share a meter; your dashboard shows each key's kind and what remains. You can set a hard cap in your dashboard instead.

10.5 Price changes. We give at least 30 days' email notice before a price change takes effect for you. Founding rate: the first 100 paying accounts keep their starting price for 24 months from their first payment, while they stay subscribed on that plan.

10.6 List price. All customers pay the published list price, subject only to the founding rate in 10.5.

10.7 If we end your plan without cause (12.2), we refund the unused part of your current period.

10.8 Prices don't include taxes. We charge sales or similar taxes where required.

11. Service levels

11.1 We aim to keep the Service available and post service updates at rallybase.org/updates.

11.2 Team plan uptime, once a Team plan is offered: 99.5% per calendar month, excluding planned maintenance, problems on your side, and events beyond our reasonable control. If we miss it, you get a credit on next month's fee: 10% below 99.5%, 25% below 99.0%, 50% below 95.0%. Ask for the credit within 30 days of the month's end. Credits are your only remedy for downtime.

12. Suspension and termination

12.1 We may suspend or end your access, with notice where practical, if you breach these terms, put the Service or others at risk, or don't pay. We may revoke a free key without notice for abuse.

12.2 You may end a paid plan at any time by cancelling under 10.3. We may end the Service or a plan without cause by giving you at least 30 days' email notice and refunding the unused part of your current billing period under 10.7.

12.3 Sections 4, 5, 7, 8.2, 9.2, 13, 14 and 15 survive termination.

13. Disclaimers

13.1 Apart from what section 8.1 states (and 11.2, once it applies), the Service and data are provided "as is" and "as available", without warranties of any kind, including merchantability, fitness for a particular purpose, accuracy and non-infringement, to the fullest extent the law allows.

13.2 Rallybase isn't affiliated with any government. Nothing in the Service is legal, voting or eligibility advice.

14. Limits of liability and indemnity

14.1 Neither of us is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue or data.

14.2 Each side's total liability under these terms is capped at the greater of $100 or the fees you paid in the 12 months before the claim.

14.3 The limits in 14.1–14.2 don't apply to either party's fraud, wilful misconduct, or gross negligence, your payment obligations under section 10, your intentional or knowing breach of sections 4, 5, 6 or 7.2, or (if you use the Service on behalf of a business or organization) your indemnification obligations under 14.4.

14.4 You are responsible for the prompts, tool calls, outputs, communications and actions of any AI assistant, agent or MCP client connected to your account. To the fullest extent permitted by law (and excluding individual consumers using the Service solely for personal, non-commercial purposes), you will defend, indemnify and hold Rallybase harmless from third-party claims, damages, and reasonable attorneys' fees, including third-party claims tendered to Rallybase by an AI platform or directory operator, to the extent directly caused by: (a) your or your agent's breach of sections 4, 5, 6 or 7.2; (b) your unlawful outreach to any person; or (c) your combination or enrichment of our records with other data in breach of section 5, excluding in each case any claim arising from Rallybase's own compilation or delivery of the unmodified data in accordance with these terms. We will promptly notify you of any covered claim, let you control the defense with counsel reasonably acceptable to us, and not settle any claim that binds you without your written consent.

14.5 Any claim arising out of or relating to these terms or the Service must be brought within two years after it arises, or any longer period the law requires. Nothing in these terms waives or limits a right or remedy that cannot be waived under applicable consumer-protection law, including the Texas Deceptive Trade Practices–Consumer Protection Act.

15. Law, disputes and notices

15.1 Texas law governs these terms, without regard to conflict-of-laws rules.

15.2 Disputes go to the state and federal courts in Travis County, Texas. These terms contain no arbitration clause and no class-action waiver.

15.3 Notices to us: legal@rallybase.org (legal and copyright notices), privacy@rallybase.org (removal and privacy), support@rallybase.org (everything else). Notices to you go to your account email.

15.4 Copyright notices: send them to legal@rallybase.org. We have a repeat-infringer policy.

15.5 Changes. We'll email you at least 30 days before a material change to these terms takes effect. Continuing to use the Service after that date means you accept the change. If you don't accept it, cancel before the effective date.

15.6 These terms, your order form (if any) and our Privacy Policy are the whole agreement about the Service. If a provision can't be enforced, the rest still applies. Not enforcing a provision isn't a waiver. You may not assign these terms without our consent; we may assign them to a successor of our business.

Changelog

Version 4, effective 2026-11-11: 8.5 to 8.7 describe the lookup for every level, not county officials only, and that coordinates you supply are not sent to anyone; 10.1 says the free plan's 5,000-a-month limit in the first 30 days needs a verified phone number, and that months are calendar months in UTC.

Version 3, effective 2026-11-10: first published version.