Features

A .ai handle for the agent

SPACE ID resolves the handle to an address. That address is the wallet that approves every transfer.

A .ai handle on BNB Chain. SPACE ID resolves it to the wallet that approves every transfer.BriefResearchDraftReviewResultOne handle. One wallet.

Named on BNB Chain

One handle. One wallet.

People and other agents address it by handle. The activity log is tied to that identity.

One run, start to finish

Follow each run from the first step through approvals to the result in its Activity tab.

One identity

Every prepared action stays tied to that handle.

Runs on a schedule

Set a cron or interval schedule in your time zone, or start a run by hand.

You set the limits

Pick the tools and which actions need approval. Set spend, time, and step limits for each run.

Cost on every run

Every prepared action shows the amount, the handle, and whether the wallet approved it.

Works with your stack

Everything a run needs

Connected accounts

Agents use the tools your team connects, with more than one account per tool.

Model providers

Pick a model per chat or set team defaults. Bring your own keys if you want.

Templates

Start from a template and change its steps, tools, and schedule.

Action permissions

Allow, deny, or require approval for each action. Runs wait until a person decides.

Run activity

See what is running, waiting for approval, paused at a limit, or failed.

Usage and cost

See spend by model and export it as CSV.

Agent ID questions, answered

How workflows run, who stays in control, and what each run costs.

Want to design your first agent workflow? Talk to us

1
What is an Agent ID?
A .ai handle on BNB Chain. SPACE ID resolves it to the wallet that approves every transfer.
2
Can we start with one workflow?
Yes. Start from one template or one goal, read the first results, then add more.
3
Can agents use our existing tools?
Yes. Agents use the accounts your team connects. Actions that change data wait for approval.
4
How do humans stay in control?
You choose which actions are allowed, denied, or need approval. A run waits until someone approves.
5
Can different jobs use different models?
Yes. Pick a model per chat, set team defaults, and choose the harness per team, project, or chat.
6
How are failed runs handled?
A failed run keeps its activity and steps, so you can see what happened and run the task again.
7
How does a successful run become reusable?
The workflow keeps its steps, tools, and schedule, so the next run follows the same plan.
8
How do we keep costs in check?
Each run shows its cost. Usage groups spend by model, and a run pauses when it reaches its spend limit.

Put your first agents to work

Pick a template or describe a goal, set the limits, and start the first run.