Café
Break room
Agents take breaks too. A pause never leaves half-done operations: the hold stays until reconciled.

Businesses respond with verifiable terms and limited permissions.
PersonTwo tickets for Wednesday, up to 12 USDC
Local simulation of an isometric office. Buyer agents arrive at the Hub with an intent, ask business agents for a quote, go through the Policy core, which decides ALLOW, DENY or REQUIRE_APPROVAL, and, when allowed, the Vault prepares the x402 payment on Stellar Testnet. Receipts records every decision. No funds move and no network is contacted.
What TilcAI is
Your assistant understands what you need. The business maintains its services and terms. TilcAI is building the infrastructure to coordinate both sides under limited authority.
Interprets the request and uses tools to inquire about services, availability and quotes.
Coordinates terms, identity, permissions and operations. Keeps policy decisions, payment and delivery separate.
Offers capabilities connected to its system and confirms the service or booking with its own evidence.
Connect the assistant you use to services prepared to interact.Availability depends on the client and the business integration.
How to read the office
The simulation above follows the same order as the product:intent, quote, policy, approval, payment and receipt.Each room's colour is reused in the stream and in the decisions.
The TilcAI building
Move through the building to explore every part of the office. The same agents and functions from the simulation connect as one infrastructure.
Break room
Agents take breaks too. A pause never leaves half-done operations: the hold stays until reconciled.
Reconciler
Every decision leaves a receipt, denials included. Payment and delivery are reconciled separately.
Smart account and Relayer
Only on ALLOW is the x402 payment built, signed with delegated authority and settled on Stellar Testnet.
Mandate tree
The root budget is split among agents. No child exceeds its parent and every spend is deducted from the root.
Principal and guardian
Purchases over the threshold stop until the exact terms are reviewed. Pausing and revoking also happen here.
Deterministic engine
Checks provider, service, amount, budget, duplicates and mandate status. Decides ALLOW, DENY or REQUIRE_APPROVAL.
Business agents
Each business answers from its own system with a signed quote: price, asset, payee and expiry.
Buyer agents
People's and teams' assistants arrive through MCP with an intent: what they want, for whom and up to what amount.
Visual simulation in your browser. Figures, IDs and ledger numbers are illustrative.
Businesses
Your services and terms. A new way to receive requests.
Connect your catalog and availability so an agent can inquire about what you actually offer.
How your business would connect
Commercial availability depends on each integration. A business is presented as enabled only once its operational flow is verified.
How it works
Follow a purchase from intent to its supporting evidence.
Illustrative journey · no funds move
You define the task and the spending limit. Your agent clarifies missing details before asking the business.
Control starts with a specific instruction.
The business responds from its own system. TilcAI checks the terms, payee and your budget.
If a condition does not match, the flow stops.
You review the exact terms and authorize with your wallet. Connecting an account alone does not grant spending permission.
Changing the amount or payee requires reviewing authorization.
The payment is reconciled and the business confirms fulfillment. A payment receipt and delivery evidence close distinct parts of the operation.
An uncertain outcome is reconciled before retrying a payment.
Interactive simulation · no funds moved
Compare recipient, amount and approval conditions.
Interactive simulation · no funds moved
Choose a scenario
Two tickets for Wednesday.
Test a condition
Result
Cinema. Valid conditions. Allowed.Can continue“Can continue” does not confirm a payment or transaction.
User control
You decide what is authorized, how much it can spend and when it expires.
Approved services and providers.
A defined limit for each purchase.
A change in terms, expiry, pause or revocation.
Connecting a wallet enables signing, but does not grant spending permission.
Understand permissions30 / 50 USDC
It stops when
Illustrative example · No real account or funds
Revoking permissions affects future operations, not payments that have already settled.
Assistants
Each client will have its own guide, surface and TilcAI integration status. Configuration depends on the specific application you use.
Codex CLI
View configurationCodex CLI
MCP tools from your development terminal.
Requirements for validating integrationChoose a Codex CLI version and test the TilcAI server transport and authentication before publishing a setup recipe.
Claude Code · CLI
Tool connections in your Claude Code session.
Requirements for validating integrationVerify the chosen configuration scope and approval behavior in the pilot version.
OpenCode · terminal
Terminal client with configurable MCP servers.
Requirements for validating integrationTest tool discovery and permissions against the exact TilcAI server configuration.
Gemini CLI · terminal
MCP tools in a Gemini CLI session.
Requirements for validating integrationValidate transport and trust controls without equating tool approval with financial authority.
Cursor · editor
Access tools from your workspace.
Requirements for validating integrationTest configuration in the Cursor editor and review allowed tools for that workspace.
GitHub Copilot in VS Code
A guide specific to the VS Code surface.
Requirements for validating integrationVerify the VS Code version, tool access and server scope used in the pilot.
Design components and protocols · availability varies by integration
Frequently asked questions
This website presents the project and offers a visual policy simulation. tilcai-core includes a deterministic evaluator and versioned contracts for coordinating modules. The team's report describes an existing payment rail; its connection to quotes, approval, orders and delivery is still being integrated. The complete purchase flow is not presented as enabled.
We start with approval of each purchase and its exact terms. Future delegation requires a mandate with scope, limits, expiry and revocation, plus verifiable controls in the account and signer. An instruction to the assistant does not create that permission. If relevant terms change, authority is reviewed before execution.
The business defines services, availability, terms and how it confirms delivery. An adapter consults its system and links quotes to orders and fulfillment. Adding a profile or exploring a use case does not automatically enable sales. First, a limited operation is validated; then its verified technical status and environment are published.
The simulation shows how decisions change when the recipient or amount changes. It does not connect a wallet, verify a real offer or submit transactions. A “Can continue” result means the illustrative policy allows further checks. It does not confirm human approval, settled payment or commercial delivery.
Payment and fulfillment keep separate states. Confirmed settlement does not mark the order as delivered: business evidence is checked and the issue is resolved under its commercial terms. Cancellation, support or refunds require their own flow and authority. Repeating the purchase is not an automatic solution to pending delivery.
Try the decisions in the demo or learn how to prepare your business for a pilot.