90-day pilot
No-cost demonstration
$0 setup. Citehouse bears the indexing, hosting, and indemnification underwriting cost of the pilot. Society retains all rights and customer-approval authority.
For societies
Your corpus, agent-callable. White-labeled, with revenue back to your society.
AISC shipped Clark. NFPA shipped LiNK. ICC shipped AI Navigator. ASCE shipped Eaves in April. Every other engineering society will need an agent-callable, paid endpoint on its corpus within twelve months. Citehouse builds yours, white-labeled to your brand, with a per-call revenue split back to your society — for less than a tenth of what an in-house build would cost.
The shape of the problem
Your members are already querying AI over your standards. You are not paid for it.
Open any AI copilot used by a structural engineer, a piping engineer, a vehicle systems engineer, a water utility engineer. The model has read your standards. The user is asking it questions that resolve to your specifications. The retrieval is uncited, uncompensated, and uncontrolled.
Citehouse turns that channel into a paid one without asking your team to build, host, or operate anything. The society publishes the standards. Citehouse hosts and meters the gateway. The agent builder pays per call. Money settles back monthly.
- — You keep your IP, your brand, and your distribution rights.
- — You see, per-customer, what is being queried and how often.
- — You decide who is allowed to integrate and on what terms.
Partnership model
70/30 society-favorable. No exclusivity. Terminable for any reason.
Production cutover
$35,000 one-time setup
Custom DNS, society admin console, indemnification underwriting, full-corpus indexing. Recovered out of revenue inside the first year at typical volumes.
Recurring economics
60–70% of attributed revenue
70/30 society-favorable during pilot. 60/40 after the earlier of 12 months post-pilot or 100M tokens. SLA monitoring at $1,500/mo covered out of the society's share.
How it works
One contract on your side, many builder integrations on ours.
Citehouse signs the agent-builder customers. Each call resolves to an attributed ledger entry on your corpus. We pay you monthly via Stripe Connect.
Sample retrieval citation, returned with every call:
ASME B31.3 §304.1.2AWWA M11 ch. 4
FAQ
Common questions from society leadership.
- Why does this need to happen now?
- Your members and licensees are already querying AI agents over your standards. AISC, NFPA, ICC, and ASCE built and shipped agent-callable channels in the last 18 months. The remaining societies will need the same channel inside twelve months. Citehouse exists because most do not have the engineering bench to build it themselves.
- Who owns the corpus and the brand?
- The society. Citehouse never holds the rights and never operates a Citehouse-branded surface to your members. The agent-callable endpoint is hosted on a society-controlled subdomain or an agents.<your-society>.org redirect. Your wordmark, not ours.
- What does the pilot commit us to?
- A 90-day pilot at $0 setup cost. The society retains all rights, sets the customer-approval list, and can terminate for any reason. The pilot is non-exclusive. Citehouse bears the indexing and gateway-provisioning cost during the pilot as the cost of the demonstration.
- How is revenue split?
- 70% to the society, 30% to Citehouse during the pilot. The split ratchets to 60/40 at the earlier of 12 months post-pilot or crossing 100M tokens served from your corpus. Anchor societies (the first to sign) get 75/25 for the first 12 months.
- What happens if a competitor wants to integrate?
- You decide. The default during pilot is allow-list: Citehouse does not onboard a builder customer without your written approval. After the pilot, you can move to allow-list, deny-list, or open-access on a per-customer basis.
- How does Citehouse protect against retrieval errors?
- An eval harness runs nightly against a held-out test set per corpus. Citation correctness is a published number visible to the society and to builder customers. If retrieval drops below the contractual floor, the society is notified before the end-user, and SLA credits to builder customers are automatic.
- What about indemnification?
- The society warrants the rights to its content. Citehouse warrants faithful retrieval and citation. The builder customer warrants application correctness in their product. Three parties, three warranties, no overlap. Counsel-reviewed templates available on request.
Ready to see the pilot template?
Counsel-reviewed, society-favorable, and short. Citehouse responds within two business days.