The Noded SDK
Bring your entire customer stack into your app.
The @bigfootai/noded-sdk drops your live Noded graph - people, accounts, activity, notes, memory - straight into a CRM sidebar, a support widget, or an internal dashboard. One-line auth, typed helpers, no GraphQL to learn. Vibe-code it with Claude or Cursor.
Need more than the helpers cover? The Graph API reference documents every operation the SDK sits on. Not building an app at all? See the other ways in →
Quickstart · 5 minutes
From zero to live data
Create a personal access token in Noded, keep it on your server, and every call runs as you - scoped to exactly what you can see in Noded. No OAuth ceremony, nothing to provision, revoke it any time.
Create a token
In Noded, open Settings → Developer and create a token. It is shown once - store it as a server-only secret, for example NODED_PAT.
Install & connect
npm i @bigfootai/noded-sdk, then create the client with mode: 'token' in your server code - a server function, an API route, an edge function.
Read
Call the resource helpers. No GraphQL, no schema spelunking - just typed results.
import { Noded } from '@bigfootai/noded-sdk'; // runs on your server; the token never reaches the browser const noded = new Noded({ auth: { mode: 'token', getToken: () => process.env.NODED_PAT }, }); const people = await noded.people.search('acme.com'); const [acme] = await noded.accounts.search('Acme'); const timeline = await noded.activity.forTag(acme.id, { limit: 20 }); const note = await noded.notes.create({ title: 'QBR prep' });
Reference
What you can pull in
Every helper returns clean, typed objects. Need a field the helpers don't cover? Drop to noded.graphql() and query the API directly.
| Call | Returns |
|---|---|
| noded.people.search(q) | People (contacts) matching a name or email |
| noded.accounts.search(q) | Accounts matching a name or domain |
| noded.activity.forTag(id) | Unified timeline - notes, emails, tasks, messages, meetings |
| noded.notes.create({ title }) | A note written back into the graph |
| noded.memory.forTag(id) | What Noded remembers about a person or account |
| noded.search(q) | People and accounts in one call |
| noded.graphql(query, vars) | Escape hatch - any Noded GraphQL operation |
Vibe code it
Let your agent do the wiring
Drop our AGENTS.md into your project (or .cursorrules / CLAUDE.md). It teaches Claude or Cursor the SDK, the auth model and the data shapes - so a one-line prompt produces working code, not guesses.
The agent installs the SDK, wires noded.connect(), resolves the account, and renders the timeline + memory - using the typed helpers it already understands.
Auth, without the ceremony
No secrets in the browser
A personal access token acts as the Noded user who created it. It lives on your server, every call respects that user's permissions, and revoking it in Settings → Developer stops the app at once.
Token mode
Server functions, API routes, edge functions, Lovable apps: mode: 'token' with the token read from a server-only secret. This is the path for every app today.
Server proxy
Rendering in the browser? Run a tiny proxy that holds the token and point the SDK at it with endpoint; the browser never sees the credential.
Sign in with Noded
Per-user OAuth sign-in for browser apps is coming. Tell us what you're building and we'll let you know.
Build customer-aware software.
Skip the customer-context problem - governance, ontology and model routing are handled underneath. You just render the data.