External data, under your governance.
For organizations that need custom licensing, private deployment, or marketplace data governed by the same policies as their internal data.
Beyond self-serve plans
Custom licensing
Negotiated terms with providers for internal redistribution, model evaluation or bulk use — where the provider agrees.
Private deployment
Licensed datasets inside your cloud, data center or air-gapped network.
03Governed access
Marketplace data under Data.co Control policies, approvals and audit logs.
04Dedicated integrations
Pipelines, matching and delivery built for your systems.
Security review
Documentation for your vendor-risk process, DPAs where applicable.
Support terms
Response targets and escalation set in your agreement.
What we can commit to today
The marketplace has one provider, LAW.co. Its court opinions, case summaries and citation graph are live over the API and MCP; bulk access still waits on a written rights agreement. An enterprise engagement today means scoping: confirming which datasets you need, the licensing that requires, and the deployment model — so bulk or private access can start as soon as rights are in place.
We do not make SLA, certification or compliance claims for marketplace access unless they are written into an enterprise agreement.
What is ready is the access model. API keys are organization-scoped with explicit scopes; every billable request writes one usage event that snapshots the license terms in force; denied requests are written to your audit log; and bulk channels are refused in code unless a provider has confirmed redistribution rights. Those controls are the basis for the commitments an enterprise agreement can make.
Where self-serve ends and enterprise begins
Self-serve plan quotas as configured today. Enterprise terms are set per agreement.
| Pro | Business | Enterprise | |
|---|---|---|---|
| Price | $149/month | $799/month | Quoted per engagement |
| API requests per month | 50,000 | 500,000 | By contract |
| MCP calls per month | 5,000 | 50,000 | By contract |
| Seats | 10 | 50 | By contract |
| Dataset tiers | Free, standard, premium | Free, standard, premium | All, including enterprise and contact |
| Single sign-on | — | OIDC | SAML |
| Private deployment and custom licensing | — | — | Available where providers agree |
External data under the same controls as internal data
Enterprises usually care less about any single dataset than about who uses external data, for what, and with what record.
Purpose and approval policies
Route agent and application traffic through Data.co Control gateways so that use of a marketplace dataset can require a stated purpose or a human approval.
Agent identities
Give each agent its own identity, act on behalf of named users, and evaluate requests as both, with the stricter result applied.
Audit and usage evidence
Usage events by dataset and channel, denied requests in the audit log, and exports for your own review processes.
License awareness
Every record carries its license id and access restrictions, so downstream tools can block uses a license forbids, such as bulk copying or model training.
How an enterprise engagement runs
- 1
Requirements
Datasets, use cases, volumes, environment and compliance constraints.
- 2
Licensing
We work with providers on terms that fit your use.
- 3
Architecture
Hosted, private connection or private deployment.
- 4
Agreement
Commercial terms, support and data processing terms.
What to bring to the first conversation
- The datasets or data domains you need, and why
- Who will use them: people, applications, agents
- Expected volumes by channel: API, MCP, bulk
- Where the data must live and where queries may run
- Uses that need explicit license terms, such as model evaluation
- Your identity provider and audit requirements
- Procurement and security review steps and timelines
Questions buyers ask
Can we use marketplace data to train models?
Only where the provider's license allows it. LAW.co's current terms prohibit training on its corpus without a written agreement.
Is enterprise pricing published?
No. Enterprise agreements are quoted per engagement.
Can we start on Business and move to Enterprise later?
Yes. Integrations built on the self-serve API keep working; an enterprise agreement changes limits, entitlements and terms, not the API.
Can you sign our DPA or complete our security questionnaire?
We can review your documents during scoping. What we can commit to depends on the deployment model, and we will not claim certifications we do not hold.
Can enterprise customers get LAW.co data in bulk?
Not today. Bulk access to LAW.co data needs the pending written rights agreement and counsel sign-off. We can scope your requirements now so terms can be proposed once rights are in place.
Do you support air-gapped environments?
Private deployment is designed for disconnected networks, with signed offline updates, where the provider's license permits a hosted copy.
Can marketplace data and our internal data share one set of policies?
That is the design intent of Data.co Control: the same identities, purpose conditions, approvals and audit logs apply whether an agent reaches an internal system or a marketplace dataset.
Who do we work with during an engagement?
A named contact on the marketplace team for licensing and scope, and technical contacts for integration and deployment, set out in the agreement.
Start an enterprise conversation.
Tell us the data you need and the constraints you work under.