# AI Agents in Orchestra: Signed, Autonomous, Verifiable Execution

By [Orchestra](https://paragraph.com/@orchestra) · 2025-07-11

---

Orchestra just crossed another major milestone in its mission to bring the real world onchain: AI agents are now first-class participants on the chain.

With the latest update, Orchestra now supports **onchain AI co-agents** — identities that can **observe blockchain events, reason over state, and submit verifiable signed actions**, all governed by Orchestra’s modular permission and trust architecture.

This feature unlocks a new design space for **trust-minimized automation**, **agent-assisted workflows**, and **programmable coordination** that can bridge human, institutional, and machine intelligence on a single onchain system.

* * *

### Why Onchain Agents?

As coordination between humans, institutions, and autonomous systems becomes more complex, the ability to delegate trusted action — not just read access — becomes essential.

Orchestra has always emphasized a developer-first, modular architecture. With agents, that modularity now extends to **AI-native actors** that can:

*   **Listen** for relevant events or state changes
    
*   **Reason** about what to do (based on code, rules, or ML outputs)
    
*   **Act** on behalf of users, organizations, or themselves
    
*   **Prove** what they did using cryptographic signatures and structured logs
    

This isn't theoretical. It's composable, modular, and available today on Orchestra’s Layer 1.

* * *

### What This Enables

**AI co-agents** in Orchestra can be used to automate and verify actions like:

*   **Monitoring asset transfers** and reacting to suspicious behavior
    
*   **Co-signing claims or credentials** based on external data feeds
    
*   **Maintaining supply chain workflows**, scheduling inspections, or releasing payment milestones
    
*   **Responding to events** using webhook inputs or block polling
    
*   **Executing rule-bound programs** using Orchestra’s native rule engine and programmable transactions
    

All without relying on external sequencers, offchain oracles, or bridges.

* * *

### How It Works

The core of the update introduces **agent identities** — declared during registration with an `"agent": true` flag. These identities can sign actions and responses, and are recognized by the chain as verifiable autonomous actors.

Two new transaction types have been introduced:

*   `EXECUTE_AGENT_ACTION`: Allows an agent to submit a signed payload that represents a verifiable execution step, such as executing a program or submitting a transaction on behalf of a user.
    
*   `SIGN_AND_COMMIT_RESPONSE`: Allows an agent to publish a signed output (e.g. inference result, evaluation proof, external claim validation) and store it under a dedicated namespace. These responses are fully auditable, traceable, and recorded in event logs.
    

Behind the scenes, Orchestra validates the agent’s signature, verifies the agent’s registered identity, and dispatches the action to the correct handler — just like it does for all modular feature logic.

Agent signatures use the same cryptographic model as validator or user identities, and can optionally be restricted by **ACL roles**, **collective approval**, or **governance credentials**.

* * *

### A Foundation for AI-Native Coordination

What makes this more than just another automation system is how **deeply composable** it is.

AI agents on Orchestra aren’t isolated bots or external services. They’re onchain citizens, governed and permissioned like everyone else:

*   They can be delegated authority by real users or organizations
    
*   They can issue credentials, interact with assets, or submit votes
    
*   They can participate in governance, if granted a role or collective seat
    
*   They can be revoked, audited, scheduled, or trusted — just like humans
    

In this way, Orchestra doesn’t just expose an API for automation. It establishes a **formal interface between human and artificial coordination**, with programmable, signed, and auditable semantics at every level.

* * *

### Real-World Use Cases

Some use cases we expect to see built on top of agent identities include:

*   **Compliance agents** that monitor rule violations and file automated claims
    
*   **Climate impact bots** that tag assets based on offchain emissions data
    
*   **DePIN keepers** that trigger reward releases based on uptime or proofs
    
*   **Regulatory co-signers** that verify document submissions or credential claims
    
*   **AI-powered wallets** that manage custody and approval on behalf of a DAO or user
    

These systems are no longer futuristic. With Orchestra, they’re feasible now — with composability, security, and traceability baked in.

* * *

### Building With Agents Today

Agents can be registered using the existing identity flow, with an `"agent": true` flag. Developers can then use Orchestra’s CLI and RPC endpoints to:

*   Submit signed actions
    
*   Store and retrieve signed responses
    
*   Schedule actions using the built-in scheduler
    
*   Link agent behavior to assets, rules, or webhooks
    

* * *

### What’s Next

With agents live, Orchestra is ready for more autonomous, AI-driven, and rule-bound systems to take shape.

Orchestra is becoming a trust layer not just for blockchains — but for coordinated systems of **humans, machines, and institutions**.

Let’s build that future — together, and onchain.

---

*Originally published on [Orchestra](https://paragraph.com/@orchestra/ai-agents-in-orchestra-signed-autonomous-verifiable-execution)*