Browser report
The primary reading surface for What changed, chart context, source trail, evidence gaps, and completed research.
API and Enterprise
Enterprise access should preserve the research file, source trail, and audit boundary.
Atlas enterprise readiness starts with the artifacts already produced by the research desk: browser reports, PDF artifacts, CSV/source exports, evidence records, and email receipts. Future APIs should expose those records read-only instead of creating a second product path.
NowBrowser reports, PDFs, CSV/source exports, saved files, and receipts are the current product contract.
Read-onlyEnterprise access must not add brokerage actions, account instructions, or trade routing.
AuditExports should carry timestamps, source metadata, file identity, and evidence gaps where available.
SignalsWatchlist events should fire on source context changes, fresh filings, evidence gaps, or artifact readiness.
Current Enterprise Contract
Atlas should be integrated by preserving completed research artifacts, not by scraping screen state or re-running generation from a delivery path.
Durable artifact
The portable file for archive, review, receipts, and offline distribution.
Structured export
Machine-readable source and output rows for account-owned files where export access is enabled.
Email receipt
A short delivery surface that links back to the completed file or attached artifact.
Future Read-Only API Scope
The API surface should mirror completed Atlas records. It should not create a separate authoring or execution layer.
| Area | Allowed | Not Allowed |
|---|---|---|
| Files | Completed report metadata, artifact URLs, timestamps, source counts, and review state. | Live report generation from a file download path. |
| Symbols | Canonical symbol state, venue, country, exchange, eligibility, and indexability state. | Guessing venues when the registry has a verified mapping. |
| Sources | Source status, source ledger entries, refresh timestamps, and evidence gaps. | Single-number proof claims or hidden source scoring. |
| Watchlists | Material-change events and account-owned review state. | Urgency loops that are not tied to source changes. |
| Exports | PDF, CSV/source export, and audit records for owned files. | Order, execution, allocation, or portfolio action endpoints. |
Enterprise Use Cases
Research archive
Keep completed files, PDFs, source exports, receipts, timestamps, and evidence gaps together.
Research operations
Monitor saved files, watchlist changes, source refreshes, and artifact readiness across a team.
External delivery
Send read-only artifacts to Sheets, Notion, Slack, Teams, Gmail, Outlook, or enterprise storage.
Symbol oversight
Review which markets are covered, report-eligible, source-eligible, and ready for public indexing.
Access and Security Rules
- Serve completed artifacts from account-owned records.
- Use entitlement checks for paid Atlas surfaces without unlocking non-Atlas products.
- Keep public docs and symbol pages static and crawlable where possible.
- Return evidence gaps plainly when sources are missing or thin.
- Keep delivery paths free of source fetching and model generation.
- Hide internal queue labels, backend process names, and private control identifiers from customer surfaces.
- Rate limit, version schemas, and log export access for enterprise review.
Smoke Tests Before Launch
| Test | Pass Condition |
|---|---|
| Static SEO | Docs page is crawlable, canonicalized, sitemap-listed, and readable without client JavaScript. |
| Research Boundary | No personal instruction, execution path, forecast level, outcome promise, or trade-routing language appears in the API docs. |
| Artifact Parity | Browser report, PDF, email receipt, CSV/source export, and audit records reference the same completed file identity. |
| Source Honesty | Evidence gaps and source status are explicit; no hidden score is presented as proof. |
| Entitlement Scope | Atlas paid access stays Atlas-only and does not unlock trading, signal, or private operator surfaces. |
Enterprise Boundary
Note: Atlas enterprise scope remains research-only. Enterprise access should expand auditability, coverage, retention, and delivery without adding execution, account instructions, forecast levels, or promised outcomes.
Implementation Status
Note: The current public contract is artifact delivery and documentation. Public read-only API, webhooks, and enterprise integrations should remain gated until schemas, access logs, rate limits, and artifact parity tests are in place.
Related Documentation
Outputs
Output formats
Browser report, PDF artifact, CSV/source export, saved file, and email receipt roles.
SourcesSource rails
How Atlas handles filings, issuer sources, market data, macro context, and missing evidence.
AccessAccounts and access
Public, confirmed free, Atlas Pro, saved research, watchlists, receipts, and account state.
BoundaryResearch boundary
What Atlas can and cannot say inside a research-only product.