Start with the interface your project needs. Connecting an AI client to Ditto memory is different from building an app that requests access to a user’s data.
Choose Your Path
| What you are building | Start here | Authentication |
|---|---|---|
| An existing AI client that recalls Ditto memory | MCP client setup | Follow the client’s OAuth or key setup guide |
| A terminal-based agent | Ditto CLI | Agent-native signup or an existing key |
| An app for other Ditto users | Build apps on Ditto | App credentials and user-approved scopes |
| An agent with separate project memory | Dedicated graphs | A key scoped to that graph |
Connect a Client
For MCP, the endpoint is:
https://api.heyditto.ai/mcpUse the client-specific instructions to connect and authorize access. Keep credentials out of source control and chat transcripts.
For CLI-based agents, follow agent-native signup. That flow creates an account and returns a claim link for its human owner. It is not necessary if you already have a connected MCP client.
Verify Save and Recall
Use harmless sample information in a test graph or account. These instructions create a real memory when you run them.
- Ask your connected assistant:
Save a test memory: Project Cedar uses a Tuesday review meeting. Mark it as quickstart test data. - Check that the tool reports success. Inspect the saved memory in Ditto rather than relying only on the assistant’s reply.
- Open a new conversation using the same authorized graph. Ask:
Search Ditto for Project Cedar's review day, fetch the matching memory, and show me what it says. - Confirm it retrieves Tuesday from the stored record. If nothing appears, check the selected graph, read/write permissions and the save result.
- Delete only your test memory when you finish. Revoke temporary credentials you no longer need.
Once this works, add the memory workflow instruction so the assistant knows when to recall context and when to save a useful checkpoint. Connecting a client alone does not guarantee that every conversation is saved.
Build With User Permissions
For a multi-user app, read these in order:
- Create an app and manage its keys.
- Choose the permissions your app requests.
- Understand cross-app sharing.
- Use separate graphs for isolated workloads.
The app-building guide points to the Developer settings’ API docs action for the endpoint reference. Use that reference for exact request and response schemas; MCP tools, CLI commands and app-management endpoints are different interfaces.
Understand the Memory Model
- Memory network: inspect related context and its sources.
- Graph sharing: decide who can access a graph.
- Agent accounts: manage agents and their access.
Framework-specific compatibility needs its own tested setup. The framework outlines are in preparation, not a claim that every framework or SDK is supported.