Developer Terms

athna will have a public API and an MCP server, so you can build on your workspace and connect it to the AI tools you already use. Neither is open yet. When they are, these terms apply to them, and we'll expand this page before the first key is issued. They're part of the Terms of Service.

What you get

• API keys are created in Settings → Developers, per brand workspace, with the scopes you choose. A key acts as you, within those scopes, in that workspace.
• The MCP server lets an AI assistant you run (Claude, or another that speaks MCP) read and act on your workspace through the same keys and the same scopes.
• Rate limits apply per key and are shown where you create it. Ask if you need more.

What you agree to

• Keep keys secret. A key is a password. Don't put it in a public repository, a client-side app, or a screenshot. If one leaks, revoke it in Settings and make a new one; tell us at security@athna.ai if you think it was used.
• Use the scopes you need. Ask for the least a tool needs to work.
• Your app, your responsibility. If you build something other people use, you're responsible for how it treats their data, and it needs its own privacy policy. Everything it does through athna still has to follow the Acceptable use policy and the rules of any account it publishes to.
• Don't bypass the product. The API is for building on athna, not for copying it out or working around a plan limit.
• Don't say we endorse you. You can say your app "works with athna." You can't use our name or the owl in a way that suggests we built it or approved it, without asking.

What we agree to

• Versioning. Breaking changes get a new version, and the old one keeps working for at least 6 months after we announce the change, unless a security issue forces our hand.
• A changelog. Every change is written up in one place, dated.
• Your data is yours. Data that flows through the API is covered by the Privacy policy and, if you need one, the Data Processing Addendum, exactly as it is inside the product.
• We can pull a key that's breaking these terms or putting the service at risk. We'll tell you why.

While it's in beta

The API and the MCP server will launch as betas. Betas change without the 6-month notice above, may go down, and come with no promises. We'll say clearly when each leaves beta.