What is Noxy?

Noxy delivers actionable, end-to-end encrypted decision requests from your AI agent to your users — on iOS, Android, web, or Telegram. Users approve or reject in seconds and your agent gets the answer back over a single gRPC call.

Noxy is not a generic push-notification network and not an execution layer for agent logic. It is the secure transport between an agent backend and the humans who must remain in the loop when stakes are high.

How it works in 30 seconds

Your agent calls sendDecision() through an Agent SDK with the user's identity and a JSON payload that describes the proposed action.
The Noxy relay encrypts the payload to every device registered for that identity and delivers it. If a device is offline, a silent push wakes it up.
The user sees the decision in your client app and chooses Approve or Reject.
Your agent receives the terminal outcome — APPROVED, REJECTED, or EXPIRED — and continues.

Heads up The decision payload is encrypted on the agent side before it leaves your process. The relay forwards ciphertext and never sees the plaintext you send to your users.

Where to go next

Get Started

Send your first decision request in under 10 minutes.

Architecture

How decisions flow from your agent through Noxy to user devices.

Decisions & Lifecycle

Decision shape, TTLs, outcomes, and polling patterns.

Identity Types

Bind devices to a wallet, email, phone, or your own user id.

Encryption & Security

End-to-end Kyber + AES-GCM, app secrets, and the trust model.

Connectors

Drop-in HITL for LangGraph and LangChain agents — pause, route, resume.

SDKs

Agent SDKs (Node.js, Python, Go, Rust) and Client SDKs (Browser, iOS, Android, Telegram).

API Reference

Agent endpoints, request and response shapes, and status codes.

Best Practices

TTLs, idempotency, retries, and handling EXPIRED outcomes.

Framework connectors

If you build agents with LangGraph or LangChain, the connectors wrap the Python Agent SDK as a drop-in graph node or HITL middleware — your agent suspends on interrupt(), the user approves on any device, and a webhook resumes the run.

LangGraph Connector

noxy-langgraph — pause graphs with interrupt(), resume from a webhook.

LangChain Connector

noxy-langchain — guard tool calls in create_agent with HITL middleware.

Two SDK families

Noxy ships with two complementary SDK families. Agent SDKs live in your backend and call RouteDecision. Client SDKs live in your user-facing app and receive, decrypt, and answer the decisions.

Family	Where it runs	What it does	Languages
Agent SDK	Backend / agent process	Routes encrypted decisions, polls outcomes, reads quota	Node.js, Python, Go, Rust
Client SDK	User device or chat surface	Registers the device, decrypts decisions, sends outcomes	Browser, iOS, Android, Telegram Bot