Use case · AI agents

Time Awareness for AI Agents

Autonomous agents need more than a date stamp. They need triggers that fire reliably, event ordering they can trust, and a tools manifest their model can consume directly. temporalBLOCK provides all three.

Give your agent the tools manifest

GET /v1/tools returns an OpenAI or Anthropic function-calling manifest of every API operation your key is entitled to call. Pass it to your model at startup and the agent discovers, selects, and invokes the right temporalBLOCK endpoints on its own — no custom dispatcher required.

// Let your agent discover and call temporalBLOCK tools autonomously.
// Fetch the manifest at agent startup, pass it to the model.

const { tools, baseUrl } = await fetch(
  "https://api.temporalblock.com/api/v1/tools?format=anthropic",
  { headers: { "X-API-Key": process.env.TBLK_API_KEY } }
).then((r) => r.json());

// Pass to your model — it will call the right endpoints itself.
const response = await anthropic.messages.create({
  model: "claude-opus-4-5",
  max_tokens: 1024,
  tools,
  messages: [{ role: "user", content: "Remind me every Friday at 9 AM." }],
});

The same catalog is also available as a native MCP server at POST /api/v1/mcp. Add it to Claude Desktop or Cursor with a single config entry — see below.

Temporal triggers — server-side, always-on

Temporal Skills let an agent create its own timers, alarms, and recurring schedules by POSTing a trigger predicate to /v1/skills. The server evaluates the trigger — the agent's process doesn't need to stay alive. Fires are delivered as signed webhooks with a consistent retry backoff.

// Create a recurring timer that fires a webhook.
// The trigger is a Spiral-coordinate predicate — no raw UTC cron strings.

const { skill, webhookSecret } = await fetch(
  "https://api.temporalblock.com/api/v1/skills",
  {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "X-API-Key": process.env.TBLK_API_KEY,
    },
    body: JSON.stringify({
      name: "weekly-friday-standup",
      trigger: {
        kind: "recur",
        rung: "wk",
        phase: 4 / 7,   // Friday
      },
      webhookUrl: "https://your-agent.example.com/fire",
    }),
  }
).then((r) => r.json());

// webhookSecret is shown once — verify X-Tblk-Signature on every delivery.
// Fires regardless of device state: screen off, app killed, or offline.
Eight trigger kinds: at (one-shot moment), after (delay from now), recur (repeating schedule), displaceFrom (displacement threshold), whenStateMatches (state-KV condition), whenPaceBelow (output-rate alert), whenPhaseRecurs (detected recurring pattern), and whenSequenceRecurs (ordered motif detection).

Phase-based triggers fire against θ (theta) — the angular time coordinate of the Temporal Spiral. whenPhaseRecurs fires when θ crosses a configured angle threshold; whenSequenceRecurs fires on a detected motif in the θ trajectory — no UTC cron strings required.

Strict event ordering with Causal Block

When multiple agent steps or distributed nodes write events, wall-clock timestamps collide within the same millisecond. Causal Block issues Hybrid Logical Clock tuples that always strictly increase — even on the same machine in the same millisecond — so your agent's event log has a total order you can replay deterministically.

Agent patterns that benefit most
  • Scheduled-task agents — create a skill at plan time and receive a webhook when the trigger fires, regardless of whether the agent process is running.
  • Long-horizon planners — anchor each reasoning step to a certified time so multi-step chains don't drift.
  • Multi-agent systems — Causal Block gives every agent a globally ordered event stream, avoiding split-brain on concurrent writes.
  • Pace-aware generation — Output Pacing tracks tokens/sec against a real clock so agents can surface accurate finish-time estimates to users.

Add to Claude Desktop or Cursor in 30 seconds

temporalBLOCK ships a native MCP server at POST /api/v1/mcp. Paste the config below, swap in your key, and the host discovers every tool your tier is entitled to automatically — no wrapper code, no custom dispatcher.

// claude_desktop_config.json  (macOS: ~/Library/Application Support/Claude/)
// .cursor/mcp.json            (Cursor: project root or ~/.cursor/)
{
  "mcpServers": {
    "temporalblock": {
      "url": "https://api.temporalblock.com/api/v1/mcp",
      "headers": {
        "X-API-Key": "tblk_live_your_key_here"
      }
    }
  }
}

// No restart needed in Cursor. In Claude Desktop, quit and reopen.
// Ask Claude: "What time is it right now?" — it will call the tool.
Tools available by tier
Litecalibrate · classify_temporal_intent · reference_clock · spiral_coordinate · causal_now · on_this_day · date_math
StandardEverything above + vision_batch · temporal_forecast · pacing_open · create_skill
ProEverything above + causal_compare · create_operation

Using a Lite key? The MCP server still lists Standard and Pro tools with an "Upgrade to …" note so your model can inform you what's locked — no silent failures. Compare plans →

Build time-aware agents today

Free Lite tier includes /v1/tools, /v1/calibrate, and server-side triggers. Upgrade for always-on Skills and Causal Block.

Join the waitlist

Related

temporalBLOCK

Calibrate your A.I.’s temporal clock

temporalBLOCK and Temporal Spiral are trademarks of COREinsights.

No tracking cookies — site preferences stay in your browser.

© 2026 COREinsights. Patent pending.