Know Your Human

Configure turns user context into a structured, user-approved profile any agent can read and update via API or tool call.

or:
How any agent reads a Configure profile
This agent uses Configure to link your memories across agents.
+1 linked
Plan a Kyoto trip that fits how I actually travel.
Reading approved profile context...
Stay in Higashiyama, visit Fushimi Inari at sunrise, keep one slow coffee morning after Nara, book pescatarian dinners nearby, and avoid back-to-back transfers.
Ask your agent...

Resolve the same end user across any agent.

A user's phone is their Configure identity. Verify it once and any agent they use afterward resolves to the same profile — no new sign-up, no re-onboarding. Each agent still only sees the scopes the user approved for it.

Get API key Copied to clipboard
Resolve phone to profile
Sign in with Configure linked
phone+1 (415) 555-0142
Make time this week to finish the Kyoto plan.
Resolving this phone to the same Configure profile...
I found the Kyoto context already attached to this user and held Friday at 10:30 to finish the plan.
Ask your agent...

End users permission what each agent gets to read.

Your agent can request profile context, but Configure keeps the permission step in the user experience and returns only the approved slices to your app.

Get API key Copied to clipboard
Apply approved profile scope
Agent wants to access your Configure profile
Identityname, location, profile summary
Preferencestravel style, diet, schedule
Memoriesprevious trips and saved context
Connected agentsFocusAI, WealthBot, +2 others
What's my name?
Reading only the slices approved for Vault...
I can't see your name because identity access is off for Vault. You can enable it in Configure if you want me to use it here.
Ask your agent...

Ship tool use without users needing to re-auth.

If the user already linked Gmail, Calendar, Drive, or Notion through any other Configure-powered agent, your agent inherits that connection — same OAuth tokens, same approved scopes, same capability. No second OAuth redirect, no second consent screen.

Get API key Copied to clipboard
Approve Gmail draft send
Send Maya a quick email with the Kyoto plan.
Creating a Gmail draft through Configure...
Approved and sent. Atlas reused the existing Configure tool connection, so no OAuth redirect was needed.
Ask your agent...

Ask about what your users and team are saying

Query high-volume user memory and internal team context together, so product and support teams can see the patterns behind the next release.

Open dashboard
Query user memory analytics
What are new users asking for before they churn?
search_users search_memories get_user_profile
Across 142,000 users, trial accounts that mention import setup churn 31% faster. The pattern clusters around CSV mapping, Salesforce sync, and admin approval before day 5.
Cohort Signal Suggested next step
18,420 trial users stuck on CSV import or field mapping ship guided import before setup step 3
7,900 workspaces asked for Salesforce sync before activation move CRM connector into setup checklist
2,140 admins waiting on approval from IT add owner invite and admin handoff flow
Ask a question...

Get started.

Hand your agent the skill file, install the SDK, or pick up the browser extension.

Tell your agent
Install the SDK
Browser extension Configure for Chrome 
# Configure

Configure is the identity layer for AI agents. It gives your app hosted auth, durable profile context, connected tools, and permissioned agent-scoped tokens.

---

## Quick Start

### Install and set up

```
npm init -y
npm install configure
npx configure setup
```

That flow writes:

```bash
CONFIGURE_API_KEY=sk_...
CONFIGURE_PUBLISHABLE_KEY=pk_...
CONFIGURE_AGENT=your-agent-name
```

### Add the model runtime

```bash
MODEL_PROVIDER=anthropic
MODEL_NAME=claude-sonnet-4-20250514
ANTHROPIC_API_KEY=...
```

Configure does not provide the LLM. Hosted auth can render without a provider key, but chat and tool execution will not work until the app has a real Anthropic, OpenAI, or OpenRouter key.

### Start from the actual agent reference

- `node_modules/configure/template/` — canonical packaged starter
- `examples/quickstart/` — repo mirror of the same starter
- `apps/agents/atlas/` — fuller production reference

Treat the packaged template as a coloring-book base. Keep the shell, keep Configure surfaces inline, and customize the brand, prompt, and domain behavior. Do not replace it with a smoke-test page.

### Hosted auth

```html




```

### Server-side profile + tools

```typescript
import { ConfigureClient, CONFIGURE_TOOLS, UI_TOOLS } from 'configure';

const client = new ConfigureClient(process.env.CONFIGURE_API_KEY, {
  agent: process.env.CONFIGURE_AGENT,
});

const profile = await client.profile.get(token, userId, {
  sections: ['identity', 'summary', 'integrations'],
});
const context = profile.format({ guidelines: true });
const tools = [...CONFIGURE_TOOLS, ...UI_TOOLS];
```

Docs: https://configure.dev/docs
Quickstart: npm install configure && npx configure setup
Template: node_modules/configure/template/