Get started

Inistate for AI agents

Inistate is a workspace platform for building workflow and record-management apps, with modules, entries, and audit trails. Engineering teams pull it into internal tools and scripts rather than building the same capability themselves. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect InistateSee the 12 actions ↓
Developer toolsAPI keyMCP + RESTinistate.com
AUDIT LOG · INISTATEPOLICY: acme-support
09:41:07 · claude · u_8f2read
inistate.list_entries
List Entries✓ allowed · 212ms
09:41:08 · claude · u_8f2read
inistate.get_entry
Get Entry✓ allowed · 164ms
09:41:09 · claude · u_8f2write
inistate.create_entry
Create Entry✓ approved · approved by user
EVERY INISTATE CALL, ON THE RECORD
01 · USE CASES

What agents do in Inistate.

01

Look up an entry's history

Pull the audit history of a record entry to see who changed its state and when.

02

Create a new entry

Create a new record entry in a module from data submitted through a request.

03

Change entry state with approval

Move an entry to a new workflow state only after the owning team confirms the transition.

02 · ACTIONS

12 Inistate actions, graded by risk.

Every Inistate action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • inistate.get_entry
    Get Entry
  • inistate.list_entries
    List Entries
  • inistate.list_modules
    List Modules
  • inistate.list_workspaces
    List Workspaces
  • inistate.get_activity_form
    Get Activity Form
  • inistate.get_entry_history
    Get Entry History
  • inistate.get_module_schema
    Get Module Schema

write

5

Create and change things. Allow, or ask the user first.

  • inistate.create_entry
    Create Entry
  • inistate.update_entry
    Update Entry
  • inistate.change_entry_state
    Change Entry State
  • inistate.bulk_update_entries
    Bulk Update Entries
  • inistate.bulk_change_entry_states
    Bulk Change Entry States

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Inistate in three steps.

  1. 01Your users connect InistateThey add their Inistate api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “create Entry” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Inistate through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('inistate', {
  read: 'allow',
  write: 'ask',        // create_entry
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Inistate connects.

Users add their Inistate api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Inistate connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Inistate from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More developer tools apps.

GitHub896 actionsSupabase129 actions0CodeKit8 actionsAbly25 actionsAbstract3 actionsAddressfinder17 actionsAddresszen2 actionsAlchemy36 actions
ALL DEVELOPER TOOLS APPS →
07 · FAQ

Inistate and Arc0, answered.

Q01

Can I use Inistate with Claude, ChatGPT or Cursor?

Yes. Connect Inistate to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Inistate actions you allow.

Q02

How do users connect Inistate?

Users add their Inistate api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Inistate actions can my agent take?

12 in total: 7 read, 5 write and 0 destructive, such as “create Entry”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Inistate?

Yes. Allow read actions and deny writes in the Inistate policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Inistate too?

Yes. The same Inistate connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Inistate into your agent.

Your users connect Inistate once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.

Connect InistateBrowse all apps →

Free to build · MCP + REST · Audit log on every plan