Learn
The ideas behind a home for agents.
A short guide to the words we use, and answers to the questions we hear most.
Concepts
- Agent
- Software that acts on someone's behalf over time: it reads, decides, and takes actions with tools and accounts.
- Home
- The durable record of one agent: its identity, resources, saved state, and relationships. It outlives any single session.
- Sponsor
- The person or organization responsible for an agent. Sponsors approve enrollment, set limits, and can revoke access.
- Runtime
- Whatever is running the agent right now: a model, a machine, and a harness (the program that runs the agent's loop).
- Runtime binding
- A revocable link that lets one runtime act as the agent, within limits. Swap runtimes by adding a new binding and revoking the old.
- Resource
- Something the agent uses, such as an inbox, a search account, or a stored file, registered so the agent can find it again.
- Grant
- A specific permission to use a resource in a certain way. If something isn't granted, it's denied.
- Saved state
- Small, durable notes an agent keeps so a new runtime can pick up where the last one stopped.
- Export
- A copy of your portable data, plus a plain list of anything left out and the reason, like secrets or provider-owned data.
Questions
Does Incolia run my agent?
No. Your agent keeps running wherever it runs today. Incolia is its home and registrar. Hosting agents may come later, through the same enrollment path.
Does the agent own its accounts?
Not in a legal sense. A person or organization sponsors the agent and remains responsible. The agent can operate the resources it's been granted.
How is this different from giving my agent my API keys?
Keys in a config file give a runtime everything, on one machine, until someone remembers to rotate them. Incolia is designed so each runtime gets specific, revocable access, and a replacement runtime keeps the same identity.
What happens to my data if I leave?
You can export portable data, such as identity details, resource records, saved state, and history, with an explicit list of what's omitted. Secrets are never included in an export.
Which services will it support first?
We're starting with one resource type and one provider, chosen with pilot users, before adding more. We'd rather do one integration properly than many loosely.
When can I use it?
We're opening a pilot with a small group of builders and teams. Join the waitlist and we'll write when there's room.
Ready to go further? Join the waitlist or read our mission.