Skip to main content
Nemofy
Book a demo

For agents

Agents need infrastructure access. Nemofy gives them a surface.

The same REST API operators and engineers use. A CLI for terminals, scripts, and AI agents that shell out to tools. The SDKs in three languages. Same authentication. Same permissions. Same audit log.

01 · Why a separate surface

Agents are a third user class.

Operators run Nemofy through the UI. Engineers script it through the API. Agents drive it through the CLI and the SDKs — the same authentication, the same scopes, and the same audit log apply. A service token issued to an agent is an actor in the audit log, not a hidden bypass.

02 · The CLI

For terminals, scripts, and agents that shell out to tools.

Install with a single command. Authenticate against your Keycloak. Drive providers, templates, routing rules, events. Pipe output. Compose with the rest of your Unix toolchain.

# Install
$ curl -sSf https://nemofy.com/install.sh | sh

# Authenticate against your Keycloak
$ nemofy auth login --tenant acme

# Trigger an event
$ nemofy events trigger \
    --app billing --type invoice.issued \
    --to email:lina@acme.com \
    --data invoiceId=INV-2026-0421

# Tail recent events
$ nemofy events tail --app billing --since 5m

# Update a routing rule
$ nemofy routing rule swap billing-otp \
    --primary MGate --fallback INWI

03 · The SDKs

Python · TypeScript · Java.

Same call surface, same authentication model, same audit story — regardless of which language your agent runtime ships in.

agent/notify.pyPython
from nemofy import Client

client = Client(
    base_url="https://nemofy.acme.internal",
    api_key=os.environ["NEMOFY_API_KEY"],
    tenant_id="acme",
)

client.events.trigger(
    application_id="incident-bot",
    event_type="incident.escalated",
    recipient={"team": "sre-oncall"},
    data={"summary": summary, "runbook": runbook_url},
)

04 · Authentication for agents

Service tokens. Scoped permissions. Audit by actor.

Issue a service token in Keycloak with the scopes the agent needs — and only those. Every CLI invocation and every SDK call records the actor in the audit log. When an agent triggers something, the audit query is the same one a human operator gets.

05 · What’s next

Designed. Not yet shipped.

Three roadmap items, labeled clearly so today’s buyer knows what they’re buying and what’s ahead.

  1. Roadmap · 01

    MCP server

    Direct tool integration with Claude, GPT, and other agent harnesses.

  2. Roadmap · 02

    Agent toolkit

    Pre-built tool definitions that wrap the CLI surface for the major agent frameworks.

  3. Roadmap · 03

    Framework adapters

    LangChain, OpenAI, Anthropic, and Vercel AI SDK adapters that expose Nemofy as a routable tool.

Book a deployment review