Timepoint Conductor
Operate the entire Timepoint stack in plain language. Ask the Conductor to find money, run a simulation, render a moment, or explore the causal graph — it picks the right services, runs and monitors the work, recovers when something fails, and reports the credits it spends as it goes. The Conductor is the authenticated home of app.timepointai.com and is available over both the REST API and MCP, so a person in the web app and an agent driving it programmatically share the same operator.Agent / MCP Usage
Drive the whole stack from one endpoint — the MCP
converse tool, auth, and an example request/response.The Find Money Flow
The Conductor can run a full Find Money flow end to end, handling the intermediate screening itself.
The Conductor calls every service through the API Gateway (
api.timepointai.com), so authentication, credits, and spend metering stay handled in one place. You authenticate the Conductor with your normal Timepoint token — the same credentials you use everywhere else.What you can ask it
You talk to the Conductor the way you’d brief a capable operator. For example:- “Find me $50k in grants for a regional arts nonprofit by September.” — it sources opportunities, runs the quick simulations, screens them down, and runs the deep simulation, then hands back the strongest leads.
- “Run a Pro simulation on the top three of those and compare the strategies.”
- “Render the moment AlphaGo played Move 37 against Lee Sedol.”
- “Show me what’s connected to the fall of Constantinople in the graph.”
- “How many credits do I have left, and what did that last run cost?”
How it behaves
It reports spend as it works. The Conductor is credit-aware. Every time it calls a tool it emits a short spend chirp — what it did, what it cost, and the running total — so you always know what a request is consuming. It tracks its own usage separately and never charges you outside the normal credit ledger. It recovers from failure. If a step errors, the Conductor doesn’t give up — it re-approaches: retrying with adjusted parameters, falling back to a cheaper path, or asking you how to proceed. Long-running Pro jobs are polled with backoff; Find Money runs are driven through their stages, with the Conductor making the intermediate selection itself when you’ve asked it to. It works on your own data — after a check. You can ask it to build on entities you’ve created before. The Conductor confirms you own (or have been granted access to) an entity before it uses it.Tuning your Conductor
You shape how your Conductor behaves through a small set of fixed options (no free-form configuration — the choices are a locked menu). Your selections are saved per account and applied to every conversation.
For example, set autonomy to
confirm every spend and spend ceiling to ask always for maximum control, or make choices for me with a 200-credit ceiling to let it run multi-step work uninterrupted up to a budget you’re comfortable with.
Available over REST and MCP
The Conductor speaks two ways:- REST —
POST /api/v1/conductor/messageswith your Timepoint token. This is what powers the chat atapp.timepointai.com. - MCP — a Model Context Protocol endpoint at
conductor.timepointai.com/mcpexposing aconversetool, so any MCP-capable agent (including Claude) can drive the full Timepoint stack from a single endpoint.