CrowdAlpha returns records that may shape real decisions. Access starts narrow and expands with proof of use, evidence depth, and downstream responsibility. The question is not only what a team can pay for; it is what a system should be allowed to see, discover, return, and carry forward.
The standard access paths are Builder Evaluation, Team, and Planetary Model packages. Evaluation pilots are scoped deployments. Enterprise access covers rights, security, deployment, usage, and SLA requirements.
Validation before access
$15K-40K / 8-12 weeks, fixed scope
For teams that know the decision they need to support, but not yet the right product boundary. A pilot keeps the question narrow: one package slice, one or two workflows, and enough evidence to decide whether deeper access is justified.
evaluation only
For approved enterprise and non-enterprise builders learning how agents should ask for governed context before any implementation workflow is scoped.
Access rule
Provisioned only after review; not for live decisions.
per year
For teams putting AgentLayer behind internal tools, controlled workflows, and approved implementation agents.
Access rule
Internal use only unless redistribution is contracted.
per year
For teams that need accountable action-ready context for a domain, not a general data feed.
Access rule
Coverage expands only where rights and end use are approved.
Rights by contract
$175K+ / quote-led
For access that cannot be reduced to a plan: multiple packages, sensitive live coverage, redistribution, embedded use, private deployment, security review, procurement, and SLA terms.
Pricing is based on scope, sensitivity, evidence depth, usage, deployment model, and downstream rights.
What access means
Governed domain coverage for teams that need accountable outside-world context.
Machine access to the same context packets, bounded by scopes, entitlements, redaction, and audit.
Agents can scout for stale assumptions, missing evidence, hidden exposure, and operational friction where access is approved.
Workflow-specific outputs that preserve evidence, uncertainty, and next-action posture.
Redistribution, embedded use, private deployment, and sensitive access stay contract-controlled.
Pricing principle
Annual Planetary Model coverage by domain, workflow, seats, evidence depth, and subscribed changes. Packages start at $75K/year.
Monthly or annual credits for authorized machine reads, evidence pulls, discovery scans, and agent workflows.
Named outputs for underwriting, routing, sanctions, exposure, operations, treasury, engineering, and agent workflows. Premium inputs price by volume and sensitivity.
Redistribution, embedded-agent use, source/data-rights revenue share, government or regulated use, and private deployment are negotiated as rights, not add-ons.
Request access
We use that to choose the smallest workable surface: Builder, Team, Planetary Model package, Pilot, Enterprise, or managed discovery workflow.
Email access requestAccess FAQ
Access defines what an authorized agent, software client, business user, or team is allowed to read, cite, automate, discover, redistribute, or rely on. The same record can carry different rights in different workflows.
Some records are harmless in a sandbox and consequential in production. Live sensitive context, redistribution, private deployment, and embedded-agent use require review because downstream use changes the risk.
A pilot answers whether a workflow deserves deeper access. It is fixed-scope validation, not a subscription tier.
Builder Evaluation is for approved interface learning. Team is for governed automation. Planetary Model packages are for accountable domain coverage. Enterprise and strategic contracts cover rights, redistribution, revenue share, and deployments that cannot be generalized.
The Planetary Model is organized by domain: maritime, tech/AI, steel and industrial work, forex and capital flows, energy, conflict, sanctions, logistics, space/aerospace, cyber, markets, commodities, critical minerals/mining, food and water, humanitarian, and political context. Access depends on rights, evidence depth, sensitivity, and workflow.
Redistribution rights, embedded-agent resale, raw bulk exports, private deployment, low-detection routing, enforcement-gap detail, and unrestricted sensitive live access.