For civil government offices
For offices with a few developers and a small budget.
An AI API for unclassified work, with a hard spending limit. Your IT contractor or developer connects it to a tool your office uses: it is not a chat app.
What to send, and what not to
Send
- Public guidance, policy drafts and reports you need summarized to a question.
- Plain-language rewrites of public notices and web pages.
- First drafts of memos, responses and checklists from your own notes.
- Code, tests and documentation for your office’s own software.
Don’t send
- Classified information, ever.
- Controlled unclassified information (CUI). Line Three does not accept CUI at launch; a CUI tier on AWS GovCloud (US) is planned.
- Personal information your office’s policy does not allow in an outside service.
- Criminal-justice information.
- Anything your AI use policy rules out.
Work that eats an afternoon.
Line Three drafts; a person checks every answer.
-
Long documents, to a question
Ask a long public document the question you actually have, and get back the sections that answer it.
which sections of this 80-page guidance change how we file quarterly reports?
-
Plain-language drafts
Rewrite notices, forms help and web pages so residents can follow them.
rewrite this notice at an eighth-grade reading level; keep the deadlines
-
Code help for small teams
If your editor lets you set a custom endpoint in the OpenAI chat completions format, point it at Line Three for review, tests and documentation on your office’s own systems. What is supported.
add input validation and tests to this form handler
Questions your office will ask.
-
Do you keep what we send?
Line Three stores no prompts or answers, and never uses them for training. Read the data policy.
-
What about public records requests?
Line Three keeps no prompts or answers, so keep any record your office needs of what staff sent or received. The account, billing and usage records Line Three keeps may be your own public records. What it keeps. How it answers legal requests.
-
Where is our data processed?
In the United States. Requests are answered by the model provider, Amazon Bedrock, in the AWS US West (Oregon) Region (us-west-2), using in-region inference. What Amazon Bedrock does with them.
-
Do you hold a FedRAMP or state authorization?
No. Line Three holds no FedRAMP (federal cloud) authorization. GovRAMP (formerly StateRAMP): not held. TX-RAMP: not held. Everything held and not held.
-
We’re a state or local office. How do we pay?
State and local offices buy prepaid credit by card, or pay monthly after use: by card, or on a purchase order with a not-to-exceed ceiling, invoiced monthly and payable net-30 (within 30 days of the invoice). Your own purchasing rules decide which applies. Line Three is not on any cooperative purchasing contract.
-
We’re a federal office. How do we pay?
Prepaid credit, by card: any amount from $100; it never expires, and any unused balance is refunded. Check with your card approving official or contracting office whether your card rules allow paying in advance for a service. By card: charged each month for the previous month’s usage, never above your cap. By purchase order: invoiced monthly, in arrears, through Wide Area WorkFlow (WAWF) in PIEE, against the order’s not-to-exceed ceiling. Both have a hard limit, so there is never an open-ended bill. See procurement.
For federal buyers. A monthly cap of $1,250 or less keeps a year’s spending within the federal micro-purchase threshold: $15,000 for most purchases (FAR 2.101, as of October 1, 2026 (another website)). Keep each prepaid purchase under it.
Annual spending above the threshold needs your contracting office’s normal competition rules; a monthly cap doesn’t change that.
Don’t split one purchase into several to stay under a threshold (FAR 13.003), and check your card’s single-purchase limit.
-
Which law governs our agreement?
Federal customers: U.S. federal law. State and local government customers: the law of your own state, with disputes in your state’s courts. The Terms, Government customers section.
One small cap, one key, then decide.
Start with a small cap on real, unclassified work before you commit more budget.