Skip to content

Nerve Agents

AI that knows your business. And can act on it.

Build Nerve Agents that understand your knowledge, work across your business systems, follow reliable workflows and bring people in when decisions matter.

Self-hosted and free to start. Bring your own model provider keys.

  1. Understand
  2. Reason
  3. Coordinate
  4. Control
  5. Connect
  6. Act

Reschedule installation

Customer request received

  1. Request
  2. Understand
  3. Decide
  4. Approve
  5. Act
  6. Done

Customer · website chat

Can you move my installation to Tuesday afternoon?

Demonstration with sample data

Inside the Console

The product behind the page

This is the Nerve Console, simplified for the page. Agents, conversations, approvals and activity live in one place, in light or dark.

Scheduling assistant

Published

Conversations

Today
  • Dana Whitfield

    Move my installation to Tuesday afternoon

  • Marcus Bell

    Do you cover the Riverside area?

  • Priya Raman

    Quote for a roof repair after the storm

Needs your approval

Move installation to Tuesday, 2:00 pm

Requested by Scheduling assistant

ApproveDecline

Activity

  • Answered from Scheduling policy
  • Looked up Tuesday in Calendar
  • Asked Sarah to approve a change

Demonstration with sample data

Nerve Agents

An Agent is more than chat

A conversation is where work starts. A Nerve Agent finds what your business knows, decides, asks a person when it should, and does the work in the systems you already use.

Reschedule installation

Conversation

Dana · website chat

Can you move my installation to Tuesday afternoon?

Nerve Agent

Of course. Let me check our scheduling policy and Tuesday's calendar.

Demonstration with sample data

Someone asks for something.

NerveMemory

Agents that know your business

Documents, policies, web pages and the things your team already knows go into Nerve Memory. When a customer asks, the Agent answers from the right source and shows where it came from.

  • Documents

    Service agreement.pdf

  • Policies

    Scheduling policy

  • Web pages

    yourcompany.com/services

  • Business knowledge

    Price list and service areas

Ask your Agent

NerveMemory

Nerve Agent

Yes. Installations can be rescheduled free of charge up to 24 hours before the booked time.

Source: Scheduling policy · section 2

Demonstration with sample data

NerveFlow

Reliable work, step by step

Some work should never be improvised. Nerve Flow runs repeatable processes across Agents, people and connected systems, the same way every time, and records each step.

Fixed step: runs the same way every timeAgent step: judgement, within limits you set
  1. Trigger

    Lead captured

    A visitor shares their details on your site.

  2. Agent decides

    Qualify with an Agent

    The Agent reads the conversation and judges the fit.

  3. Condition

    Is it a fit?

    In your area and in budget: continue.

    Otherwise: add to the nurture list
  4. Approval

    A person confirms

    Nothing is sent until someone says so.

    Needs a person

  5. Connect · CRM

    Update the CRM

    Create the lead with the whole conversation.

  6. Connect · Email

    Send the follow-up

    Email the customer what happens next.

Demonstration with sample data. A workflow you build in Nerve is shown step by step as it runs.

NerveTools

Connected is not the same as allowed

Connecting an application does not hand every Agent the keys to it. Before any action runs, Nerve Tools checks what the Agent may do, who it is acting as, which connection it would use and whether a person must approve.

Try it: change a rule and watch the request again.

Requested action

Nerve Tools

Send a follow-up email to a customer

gmail · send message

  1. Is this capability allowed?

    Yes

  2. Is this identity allowed?

    Yes

  3. Is this connection allowed?

    Yes

  4. Is approval required?

    Yes: a person decides first

Waiting for a person

Everything is allowed. A person approves the message before it is sent.

Demonstration with sample data

NerveMCP

Bring more tools to Nerve with MCP

Nerve can discover what an MCP server offers without automatically handing those capabilities to every Agent. A person reviews each one, then grants it to the Agents that should have it.

  1. 1The server lists its tools. Nerve stores them as inert information.
  2. 2A person reviews a tool and how risky it is.
  3. 3Only then can it be granted, to specific Agents, and revoked at any time.
How MCP works with Nerve

Orders server · example MCP server

  • search_ordersReads data

    Find an order by customer or number

    Discovered

  • get_customerReads data

    Read a customer's profile

    Discovered

  • create_refundChanges data

    Refund part or all of an order

    Discovered

  • delete_customerChanges data

    Remove a customer record

    Discovered

The server offers 4 tools. None is available to any Agent yet.

Example server with sample tools

Human control

People stay in the loop

Agents do the routine work and bring in a person when it matters. Nothing here is built to replace your team; it is built so they spend their time where they are needed.

Approvals
Consequential actions wait for a person, who sees what will happen, why, who asked and the details that matter, then approves or declines.
Handoff to your Inbox
When a customer needs someone, the conversation moves to your team with everything the Agent learned, and a person continues it.

Handoff

NerveAgent

Customer

I'd like to talk to someone about the price.

Nerve Agent

Of course. I'll bring in your team and pass along what we've covered.

Your team · InboxEmpty

Dana Whitfield

Priority
  • Conversation kept
  • Policy found
  • Calendar checked

Priya · your team

Hi Dana, I'll take it from here.

The Agent is handling this conversation.

Demonstration with sample data

Analytics

See what the work is doing

Conversations, leads, workflow runs, actions and approvals are counted for every workspace, so you can tell whether your Agents are helping and where people still step in.

Analytics

Last 14 days
  • Conversations

    Every conversation your Agents handle

  • Leads

    People who shared contact details

  • Workflows

    Runs, and how they ended

  • Actions

    Work done in your applications

  • Approvals

    Requests, and who decided

Conversations per dayIllustration

Illustration only. Your own numbers appear here, for your workspace.

The platform

Coordinated parts of one system

Nerve is the controlled environment around intelligence. Models sit behind Cortex; Agents get context from Memory, reliability from Flow, boundaries from Tools and reach through Connect.

NerveAgentsThe customer-facing worker: it talks, answers and asks for help.
NerveCortexCoordinates reasoning, actions and multi-step work behind Nerve Agents.
NerveMemoryGives Agents trusted context from the information your business already has.
NerveFlowCoordinates repeatable processes across Agents, people and connected systems.
NerveToolsControls what Agents and workflows can do, and how consequential actions are handled.
NerveConnectConnects Nerve with the applications, APIs and tools your business already uses.
  • Integrations
  • MCP
  • APIs

Governance and security

Control is part of the product

Giving an AI model access to your business is a decision, not a default. Nerve is built so that decision stays yours, and so you can see it being honoured.

Audit trail

  1. 10:42Agent asked to update an appointmentapproval required
  2. 10:43Sarah approved the changeScheduling lead
  3. 10:43Appointment updated in Calendarcompleted

Example with sample data

Read the security overview
01Least privilege
An Agent starts with nothing. It gets only the capabilities you give it, for only the applications you connect.
02Explicit capabilities
What an Agent can do is a named list you can read: look up a calendar, send an email, update a record.
03Execution identities
Work runs as an identity with its own limits, not as an all-powerful account.
04Approvals
Consequential actions pause for a person, with what will happen, why and who asked.
05Current authority
Permissions are checked when an action runs, not when it was set up. Remove access and it stops.
06Auditability
Approvals, changes and actions are recorded in an append-only trail you can review.
07MCP review
New MCP tools are reviewed before any Agent can use them, and a changed tool needs review again.
08Controlled integrations
Only reviewed integrations are offered, and each connection stays inside the boundary you set.

Use cases

The same platform, doing different work

These are not separate products. Each scenario is Agents, Memory, Flow, Tools and Connect arranged for the job.

A customer asks for a change. The Agent checks your policy, uses your business system, and asks for approval only when it should.

  1. 1

    Customer asks for a change

    In chat, on your site

  2. 2

    Agent checks policy

    From your documents

  3. 3

    Uses your business system

    Looks up, then updates

  4. 4

    Approval if needed

    A person decides

  5. 5

    Request resolved

    The customer is told

Deploy your first Nerve Agent

Start with one conversation your team handles every day. Give the Agent what it needs to know, connect the tools it should use, and decide where a person steps in.