The tools are the durable asset. The agent is the replaceable head.
Every new agent framework means re-wiring the same capabilities inside a different extension model. Bezalel puts them in one service with its own state, credentials, and event routing. Any agent connects with exactly two values: a URL and a bearer token.
Switching from one framework to the next stops being a migration and becomes a config change.
What your agent gets
7 capabilities · one token
01
Memory
Long-term memory shared by every agent you run. Session transcripts are banked automatically, distilled into durable facts in the background, and recalled by any runtime — with browse-and-forget controls in the dashboard.
02
Email
A real inbox your account owns, shared by every agent you give the email scope. Agents can send, receive, search, and file mail, and inbound messages become events that can wake an agent instead of waiting to be polled.
03
Money
A spend ledger and linked bank data, so an agent can log receipts and reconcile real transactions. Save a payment card in Vault for agent purchases with spending limits and your approval.
04
Texting
Pair your own iMessage number once. Agents reply on your real threads, and inbound texts wake the right agent through the event router.
05
A computer
A cloud desktop the agent can see and operate — click, type, browse — with a live view from the dashboard while it works.
06
Sandboxes
Disposable code-execution environments for builds, scripts, and experiments, provisioned on demand and shared across every runtime you use.
07
Connectors
Hundreds of third-party apps — calendars, docs, project trackers, and more — behind managed OAuth, exposed to your agent as plain MCP tools.
BezalelOne URL. One token.
How it works
01
Sign up and grab your token
Every account gets its own bearer token (it looks like bzl_…), minted in the dashboard. Scopes on the token decide which capability domains an agent can touch.
02
Paste one prompt into your agent
The setup prompt points your agent at the plane. It fetches the live setup instructions itself and registers the MCP server in its own harness — Claude Code, Codex CLI, Cursor, OpenClaw, eve, or anything else that speaks MCP.
03
Every agent shares the plane
Memory, inboxes, money, pairings, and connectors are one set of state. Switch frameworks and nothing migrates: the new agent gets the same URL and token, and picks up where the last one left off.
The whole of step two
Connect yourself to my Bezalel capability plane: fetch https://bezalel.sh/api/setup and follow the instructions. Your token is <TOKEN>.
Most tool servers wait to be asked. This one also picks up the phone.
A text to your paired iMessage number or a mail to your agent's inbox becomes an event that wakes the right agent. And the capabilities are personal: a phone number, an inbox, a wallet, a computer. Not a pile of SaaS connectors.
bezalel.network
