The company context layer

Reliable context, for every agent.

Structure what your company knows. Maintain it with people in the loop. Retrieve it from Claude, ChatGPT, your coding agent, Slack and any agent that speaks MCP, all reading the same copy.

Book a demo How it works

app.atlascontext.ai/

Atlas›Home

Good morning, Alex

New page

Search pages, skills, and change requests⌘K

Connect with MCP

Setup guide

Endpointhttps://app.atlascontext.ai/mcp/Copy

Claude CodeLast used 27 Sept

ChatGPTLast used 26 Sept

Needs your review

Review all

Update the EU payout windowPending reviewSlack agent

Add the threshold for annual-plan refundsPending reviewSupport agent

Kept once. Read by every agent.

Skills are how work gets done. Knowledge is what is true. Metrics are what words mean. Each is kept once, in Atlas, and every agent retrieves the same copy under the same access rules.

[02] The product

Three layers. Each one on point.

A context layer is only as reliable as its weakest layer, so Atlas is built as three. Pick a layer, then a part, to see it inside the app.

app.atlascontext.ai/guidance/before-you-start

Atlas›Guidance›Before you start

Read by every agentWorkspace · v6 · Maya Chen

Before you start

Read this before you answer anyone at Acme. It is short on purpose.

Tone

Plain, direct, no hedging. Say which page you answered from.

House rules

Quote a metric's definition. Never re-derive a number yourself.
Refunds above €500 go through Refund approvals. Do not promise them.
If a page looks wrong, open a change request instead of guessing.

Check first

Pricing policy, Payout schedule and Month-end close cover most questions.

guide · before you start · read by every agent

app.atlascontext.ai/skills

Atlas›Skills

Skills

Turn your team's expertise into reusable agent instructions.

New skill

All skills 6WorkspacePersonal

Month-end closeClose the books in five working days, in order, with ownersfinanceclosePublishedAMv0.1.4

Payout reconciliationMatch processor payouts to ledger entries and flag gapsfinancePublishedAMv2.0.1

Deploy runbookShip to production with a rollout window and an ownerengineeringPublishedAMv1.2.0

Incident reviewWrite the review within 48 hours, blameless, with actionsengineeringqualityPublishedAMv1.4.0

Refund approvalsWho may approve which refund, and what to check firstsupportIn reviewAMv0.8.0

Customer brief builderA one-page account brief grounded in the CRM and notessalesDraftAMv0.5.0

skill · month-end-close · v0.1.4 · published

app.atlascontext.ai/knowledge/finance/payout-schedule

Atlas›Knowledge›Finance›Payout schedule

MCAMFinance · Owner Maya Chen · v14 · edited 2 min ago

Payout schedule

When merchant payouts settle, by region, and the cutoff for each business day. Finance owns this page; agents read it before answering payout questions.

Settlement windows

Region	Window	Cutoff
EU	T+2	16:00 CET
UK	T+2	15:00 GMT
US	T+1	17:00 ET

Exceptions

Payouts above €10,000 follow Payout reconciliation and need an owner's approval.

page · finance / payout schedule · live

app.atlascontext.ai/tables/analytics.orders

Atlas›Tables›analytics.orders

BigQueryread-only14 columns · owner Data

`analytics.orders`

One row per order. Use it for revenue, refunds and regional splits; use analytics.payouts for settlement.

ColumnTypeWhat it means here

order_idSTRINGOne row per order. Primary key.

customer_idSTRINGJoins to analytics.customers.

amount_eurNUMERICNet of refunds, in euros.

statusSTRINGpaid · refunded · disputed

regionSTRINGEU, US or UK, from the billing address.

created_atTIMESTAMPUTC. Use for daily counts.

table · analytics.orders · 14 columns · read-only

app.atlascontext.ai/metrics/active-customers

Atlas›Metrics›Active customers

AgreedMetrics · owner Data · v3

Active customers

Customers with at least one paid order in the last 30 days.

Run preview

select count(distinct customer_id)
from analytics.orders
where status = 'paid'
  and created_at >= timestamp_sub(
    current_timestamp(), interval 30 day)

Result · bigquery

2,418 +6.2%

Same number in every agent.

Used by

Weekly churn notesAutomation

Board update, SeptemberKnowledge

Read 212 times this week6 agents

metric · active customers · bigquery · run preview

app.atlascontext.ai/knowledge/finance/payout-schedule

Atlas›Knowledge›Finance›Payout schedule

MCAMFinance · Owner Maya Chen · v14 · edited 2 min ago

Payout schedule

When merchant payouts settle, by region, and the cutoff for each business day. Finance owns this page; agents read it before answering payout questions.

Settlement windows

Region	Window	Cutoff
EU	T+2	16:00 CET
UK	T+2	15:00 GMT
US	T+1	17:00 ET

Exceptions

Payouts above €10,000 follow Payout reconciliation and need an owner's approval.

Share “Payout schedule”

Add people, teams or agents

Agents act as a person and never see more than that person can.

scope · finance › payout schedule › maya chen (edit)

app.atlascontext.ai/change-requests/128

Atlas›Change requests›Update the EU payout window

Edit section

Update the EU payout window

Slack agent · as Maya Chen · 4 min agoPending review0/1 approved

Why this was proposed

Finance confirmed in #payments that EU settlement moves to T+1 from 3 March.

Affected items 1

Payout scheduleAwaiting Maya Chen

Knowledge / Finance / Payout schedule / Settlement windows

Settlement windows

EU payouts settle ~~T+2~~ T+1 from 3 March (T+2 until then), with a cutoff at 16:00 CET. Payouts requested after the cutoff move to the next business day.

All changes apply together when approved.RejectApprove and apply

change request · payout schedule · from slack agent · pending review

app.atlascontext.ai/audit

Atlas›Audit

Audit

Who and which agents read or changed your context.

Today

TimeActorActionObjectSurface

09:42Slack agentreadPayout scheduleMCP · Slack

09:41Slack agentsearched“EU payout window”MCP · Slack

09:30MCMaya ChenapprovedUpdate the EU payout windowWeb

09:12Claude CodereadDeploy runbook v1.2.0MCP · Claude Code

08:58AMAlex MorganeditedPricing policyWeb

08:40Support agentproposedRefund approvalsMCP · API key

08:15ChatGPTqueriedmetrics/active_customersMCP · ChatGPT

audit · payout schedule · who, what, when

app.atlascontext.ai/automations/weekly-churn-notes

Atlas›Automations›Weekly churn notes

ActiveMondays 09:00 · Europe/Paris · your model key

Weekly churn notes

Keep the churn page in step with the metric, and ask a person before anything changes.

Run now

Read metrics/churn and last week's notes
Compare the movement with the definition
Propose an update to “Churn notes” for review

Recent runs

Mon 22 Sep · proposed 1 changeIn review

Mon 15 Sep · no change neededDone

Mon 8 Sep · proposed 2 changesApproved

automation · weekly churn notes · mondays 9:00

insights · 12 stale pages · 6 unanswered questions

claude — ~/acme/payments

Claude Code ~/acme/payments

> When do EU payouts settle, and who approves exceptions?

atlas · search_context("EU payout settlement")

⎿ 3 results · payout-schedule.md · payout-reconciliation · analytics.payouts

atlas · inspect_context("knowledge/payout-schedule.md")

⎿ v14 · owner Maya Chen · Finance · read as alex@acme.com

EU payouts settle T+2 with a 16:00 CET cutoff. Payouts above €10,000 need an owner's approval, per Payout reconciliation v2.0.1.

atlas · create_change_request("Note the T+1 move in March")

⎿ Opened for review by Maya Chen

app.atlascontext.ai/mcp · sign in as yourself

app.atlascontext.ai/search?q=refund+policy

Atlas›Search

refund policy

3 results you can open

Refund approvalsSkills · Support — who may approve which refund, and what to check first

Pricing policy › RefundsKnowledge · Workspace — annual plans are refunded pro rata within 30 days

Refund rateMetrics · Data — share of paid orders refunded in the period

Access is checked before ranking. Pages you cannot open are never returned, to you or to your agents.

search · "refund policy" · only what you can open

app.atlascontext.ai/playground

Atlas›Playground

When do payouts settle for EU merchants?

Retrieved · 3 sources

Payout schedule › Settlement windows0.92

Payout reconciliation0.81

analytics.payouts0.64

EU payouts settle T+2 with a 16:00 CET cutoff ¹. Requests after the cutoff move to the next business day ¹, and payouts above €10,000 need an owner's approval ².

Ask a question as an agent would…

playground · "when do payouts settle?" · 3 sources

evaluation · finance questions · 48 / 52 passing

[03] Under the hood

Reliable by default.

The unglamorous parts are what make context trustworthy. They are on in every workspace, for people and agents alike.

How it works

01Access: Agents sign in as a person over OAuth. Search checks access before it ranks, so an agent never sees more than its person.
02Changes: Agent edits arrive as change requests. A person reads the diff and approves it, block by block.
03History: Every save is a version. Compare any two, restore any one. Deleted pages go to a trash you can restore from.
04Audit: Every read and every write, by people and by agents, in one workspace-wide trail.
05Warehouse: BigQuery and Snowflake, read-only. A metric is SQL agreed once, so every agent gives the same number.
06Models: Atlas calls a model only when a workflow you set up runs, with the provider and key you connect.
07Hosting: Run for you by Ensemble Labs on Fly.io in Paris. One workspace per company, invitation-only.

[04] Connect

One endpoint. Any agent.

Point your agent at Atlas and sign in as yourself. It reads what you can read, and its edits come back to your team as change requests.

Your agent opens Atlas in a browser. You sign in and pick a workspace.
You approve access for this agent. It gets its own grant, never your session.
Every call checks your current access. Lose access to a page and so does your agent.

Every client

terminal

claude mcp add --transport http atlas https://app.atlascontext.ai/mcp/

Run /mcp in Claude Code and sign in.

terminal

codex mcp add atlas --url https://app.atlascontext.ai/mcp/
codex mcp login atlas

The login command opens Atlas in your browser.

.cursor/mcp.json

{ "mcpServers": { "atlas": { "url": "https://app.atlascontext.ai/mcp/" } } }

Cursor asks you to sign in the first time it connects.

terminal

code --add-mcp '{"name":"atlas","type":"http","url":"https://app.atlascontext.ai/mcp/"}'

VS Code asks you to sign in the first time an agent uses Atlas.

Settings › Connectors › Add custom connector

https://app.atlascontext.ai/mcp/

Paste the endpoint, then sign in when Claude asks. Works in the Claude app on desktop and on the web.

[05] Solutions

One layer, two ways in.

Company brainOne place your company agrees on what is true.Procedures, facts and numbers written down once with an owner, kept current by people, and read by everyone the same way.Explore

app.atlascontext.ai/knowledge/finance/payout-schedule

Atlas›Knowledge›Finance›Payout schedule

MCAMFinance · Owner Maya Chen · v14 · edited 2 min ago

Payout schedule

When merchant payouts settle, by region, and the cutoff for each business day. Finance owns this page; agents read it before answering payout questions.

Settlement windows

Region	Window	Cutoff
EU	T+2	16:00 CET
UK	T+2	15:00 GMT
US	T+1	17:00 ET

Exceptions

Payouts above €10,000 follow Payout reconciliation and need an owner's approval.

Agent memoryGive every agent the same memory.Each agent signs in as a person, reads what that person may read, and remembers through Atlas instead of on its own.Explore

claude — ~/acme/payments

Claude Code ~/acme/payments

> When do EU payouts settle, and who approves exceptions?

atlas · search_context("EU payout settlement")

⎿ 3 results · payout-schedule.md · payout-reconciliation · analytics.payouts

atlas · inspect_context("knowledge/payout-schedule.md")

⎿ v14 · owner Maya Chen · Finance · read as alex@acme.com

EU payouts settle T+2 with a 16:00 CET cutoff. Payouts above €10,000 need an owner's approval, per Payout reconciliation v2.0.1.

atlas · create_change_request("Note the T+1 move in March")

⎿ Opened for review by Maya Chen

Start with one team.

Bring one team's procedures, pages and definitions. We structure them with you, run Atlas for you, and connect the agents you already use.

Book a demo

Reliable context, for every agent.

Good morning, Alex

Connect with MCP

Needs your review

Recently updated

Kept once. Read by every agent.

Three layers. Each one on point.

Before you start

Tone

House rules

Check first

Skills

Payout schedule

Settlement windows

Exceptions

`analytics.orders`

Active customers

Payout schedule

Settlement windows

Exceptions

Update the EU payout window

Settlement windows

Audit

Weekly churn notes

Insights

Finance questions

Reliable by default.

One endpoint. Any agent.

One layer, two ways in.

Payout schedule

Settlement windows

Exceptions

Start with one team.