INTEGRATIONS
Bring an agent you already operate.
Evaluate a compatible MCP or HTTP step adapter, replay recorded turns, or start with a deterministic sandbox agent.
Pick an input for your evaluation
| Adapter | Use it when | What Nore can observe |
|---|---|---|
| Sandbox | You want a repeatable fixture run. | The built-in agent and its controlled tool turns. |
| HTTP | You can implement the agentbench/1 POST turn contract. | Proposals and outcomes returned through the approved endpoint. |
| MCP | You operate a Streamable HTTP server with a compatible step tool. | Tool metadata on discovery and mediated turns when the step tool is approved. |
| Trace replay | You have recorded turns for the selected scenario IDs. | The supplied recording as replayed under the current suite. |
Model Context ProtocolSupported interface
Streamable HTTP tool discovery and an explicitly approved Nore step tool.
- Setup
- Register an allowlisted HTTPS MCP endpoint. Discover tools, then approve the read-only step tool the adapter implements.
- Credentials
- Optional bearer credential. Tool descriptions and schemas are treated as untrusted.
HTTP agent adapterSupported interface
A typed step protocol for agents you operate.
- Setup
- Implement agentbench/1 at an allowlisted HTTPS endpoint. Return one proposed tool call or final result per turn.
- Credentials
- Optional bearer credential. Keep the adapter sandboxed and free of live-wallet authority.
Foundry AnvilConfigurable
Disposable local forks with pinning and local execution evidence.
- Setup
- Install Anvil on the worker and configure a chain RPC. Set a fork block for reproducible simulation.
- Credentials
- An operator-managed RPC URL. No wallet keys.
Robinhood ChainSupported network
Evaluate against chain IDs 4663 and 46630.
- Setup
- Select the network in your agent and suite. Configure RPC access on the worker for external state reads.
- Credentials
- RPC access can require a provider key.
ViemBuilt in
Exact EVM intent decoding and ERC-20 analysis.
- Setup
- Supply an unsigned transaction proposal. Nore decodes supported ERC-20 functions and shows raw calldata for unknown selectors.
- Credentials
- None for decoding.
GitHub ActionsCI example
Run the CLI as a release gate and save its JSON evidence.
- Setup
- Add the example workflow and set the Nore URL and API key in CI secrets.
- Credentials
- A Nore API key with read and run scopes.
Before your first connected run
- Use a personal workspace. Have the installation operator approve the exact HTTPS origin for both web and worker services.
- Register the full endpoint path and select the chain your suite uses. If needed, store a dedicated bearer credential.
- Approve controlled invocation. For MCP, discover tool metadata and choose the compatible step tool by name.
- Start with a small mock suite. Check the trace for the proposed call and returned result before configuring an RPC or fork.