Build on Nico 2.5. The GTM model, as an API.
One keyless endpoint runs the full agentic loop server-side against your connectors — sourcing, enrichment, scoring, and drafting — and streams every step back. No model keys to manage, no tool plumbing to build.
Passwordless sign-in · usage metered per token · curl · Python · TypeScript · Go
curl https://nico.macrodeep.com/v1/ask \
-H "Authorization: Bearer $NICO_SESSION" \
-d '{
"model": "nico-2.5",
"prompt": "Which open deals went quiet this
month? Draft re-engagement.",
"stream": true
}'
# Nico plans, queries your CRM, drafts —
# and holds every send for approval.
event: step research · 48 open deals scanned
event: step 14 quiet > 21 days · drafts ready
event: approval 14 held — approve in any appTwo endpoints. One account & budget.
Agent API
Hand Nico a goal. It plans the run, calls your connectors in a server-side tool loop, and streams each step — holding every outbound send for approval.
- Server-side tool loop over 75+ connectors
- Streamed step, tool, and approval events
- Approval boundary enforced server-side
- Full run trace, replayable and interruptible
Chat API
Direct, streamed access to Nico 2.5 for classification, scoring, and generation — when you want to own the loop and orchestrate tools yourself.
- Streamed tokens with usage per response
- Structured output & function-calling schemas
- Call the model by id: nico-2.5
- Drop-in familiar request shape
Get a key
Sign in with an emailed code, create a session token, and connect your stack once.
Make a call
Fire /v1/ask or /v1/chat and stream the response. SDKs for four languages.
Test & measure
Replay runs, inspect tool traces, and score against the GTM eval suite before you ship.
Ship & monitor
Set budgets, per-model caps, and rate limits. Watch usage and revoke sessions any time.
Keyless by design
The platform holds the model keys. You send a session token; we meter every call.
Connectors in the loop
75+ tools callable server-side. Credentials encrypted at rest, never shown to the model.
Approval boundary
Sends and writes are held as approval events — resolve them in any app or via API.
Streaming
Server-sent events for tokens, steps, tool calls, and approvals — render progress live.
Structured output
Constrain responses to a JSON schema for scoring, routing, and enrichment pipelines.
Plan-aware limits
Monthly budgets, per-model caps, and burst rate limits enforced on every request.
Webhooks
Subscribe to run completion and approval events to drive your own workflows.
Revocable sessions
List active sessions, scope them, and revoke instantly. Tokens live in the Keychain.
One model. One id.
API reference →
Every endpoint, parameter, event type, and error, with examples.
SDKsClient libraries →
Official SDKs for Python, TypeScript, Go, and Ruby — typed and streaming-ready.
CookbookRecipes →
End-to-end examples: re-engagement runs, ICP scoring, reply routing, enrichment.
GuidesConcepts →
Tool loops, the approval boundary, structured output, and streaming, explained.
ChangelogWhat's new →
Model releases, new connectors, and API changes — with migration notes.
StatusSystem status →
Live uptime and incident history for the API and every connector.
Ship your first run today.
Sign in with an emailed code, grab a session token, and make an agentic GTM call in minutes.