atmon documentation
atmon lets an assistant act in the apps you already use, inside limits you set, with a record of everything it did.
The problem it solves is narrow. A model can decide what to do and cannot do it: doing it means holding a real credential for a real account, sending the right request, stopping when it should not go further, and being able to say afterwards exactly what happened. atmon owns that part, so whatever you have built on top of it does not have to.
Where to go
| If you want to | Read |
|---|---|
| Get from nothing to a first action | Start |
| Do something in the console | Using atmon |
| Point an assistant at your account | For your AI |
| Call it from your own code | SDKs and the API reference |
| Look up an error, a limit, or an app | Error codes, Limits, App reference |
| Deploy, operate, or administer atmon for an organization | enterprise.atmon.ai/docs |
The four things it does
- Finds the tool. You describe the task in words; atmon answers with a ranked short list of the actions that fit, drawn from the apps that account has connected. Your assistant never carries a menu of hundreds of tools.
- Holds the credential. Sign-in flows, token refresh, and an encrypted store, per person. Nothing that calls atmon ever sees a token.
- Applies your rules before it acts. Allowed and forbidden apps, spending ceilings, calls that need a person to approve them, rate ceilings. All of them are checked before any credential is unlocked, so a refusal costs nothing and touches no external app.
- Records every call. Successes, refusals, and parked approvals alike. There is no path through atmon that acts without leaving a receipt.
Where this stands
atmon is in beta. The paths are real: requests go out over a real HTTP client, sign-in flows run for real, and every connector is held to an accuracy gate before it ships. Live accounts are beginning. GitHub has approved atmon as an application its users can connect and is the only one so far, so every other connector is still proven against a stand-in service rather than against a real inbox or a real payment account.
That boundary is worth reading before you plan around it. No connector other than GitHub should be taken as a live integration until this page says so.