ENES

Businesses respond with verifiable terms and limited permissions.

PersonTwo tickets for Wednesday, up to 12 USDC

TilcAI office: agent simulation

Tap an agent to open its card

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.

Root budget
150.00 / 150.00 USDC
Settled today
+0.00 USDC
Decisions
0
ALLOW
0%
DENY
0
Approvals
0
  • Simulation · no funds
  • Stellar Testnet · simulated
  • Relayer · sponsorship OK
  • Period 03:00
Scroll to explore TilcAI

What TilcAI is

A connection between your intent and the business operation.

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.

  1. Your agent

    Interprets the request and uses tools to inquire about services, availability and quotes.

  2. TilcAI

    Coordinates terms, identity, permissions and operations. Keeps policy decisions, payment and delivery separate.

  3. The business

    Offers capabilities connected to its system and confirms the service or booking with its own evidence.

How to read the office

Every room is a piece of TilcAI.Agents walk the full path of a purchase.

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

Eight floors. One connected journey.

Move through the building to explore every part of the office. The same agents and functions from the simulation connect as one infrastructure.

Scroll to discover each floor

Floor 08

Café

Break room

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

Scroll to discover each floor

Businesses

Your business, ready to talk to agents.

You do not need an AI agent or a website to start. You keep deciding price, availability, payout destination and delivery.

Publish your services.

Connect your catalog, availability and terms so agents can ask about what you actually offer.

Four ways to connect

Start from where you are today.

The same business can move from one path to another without losing its identity, its order history or its payout destination.

Your business, always connected
Same identity on every pathData, orders and payments unified
  • Managed console

    No software and no agent

    A private portal to publish a small catalog, confirm availability, receive requests, quote, and see orders and payments.

  • File or spreadsheet

    With a spreadsheet or a closed system

    You import your catalog from a file; it is validated and published with a version. Stock depends on you updating or confirming it.

  • API or POS connector

    With a sales or inventory system

    An adapter connects price and stock in real time, with events and tests. Holding stock depends on what your system allows.

  • Your own agent

    With a technical team

    Your server responds over an API and, later, over A2A. TilcAI keeps the checks, the order and the payment rail.

You keep

  • Prices and terms
  • Availability and capacity
  • The payout destination, verified
  • The delivery confirmation

TilcAI coordinates

  • The buyer's identity and rules
  • Quote and order with shared identifiers
  • Payment over a supported rail and its reconciliation
  • Receipts for both parties

Solutions for businesses

Businesses already implementing TilcAI.

Each business keeps its system, its customer and its charge. TilcAI joins from behind: the order, the approval, the payment and a receipt for each side.

Next implementation

Payments for Baral

Next on the list.

An integrated creative strategy agency. Its payments join the next TilcAI implementations.

The same journey

  1. Order
  2. Approval
  3. Payment
  4. Receipt

ScopeTo be confirmed with the business

How it works

One operation.Six steps.Two receipts.

Follow an order from intent to its supporting evidence. Every step has an owner and a state, and payment is never confused with delivery.

  1. 01 / 06 · Owner: Your agent

    Request

    You ask for “20 bags of cement, pick-up in store” and set a limit. Your agent clarifies what is missing before asking anyone.

    Your requestState: Requested
    • 20 bags of cement
    • Pick-up in store
    • Up to 1 USDC · this purchase only

    Control starts with a specific instruction.

  2. 02 / 06 · Owner: The business

    Offer

    The hardware store answers from its own system: price, availability with its date, expiry and payout destination. If stock was entered by hand, it stays pending confirmation.

    QuoteState: Quoted
    • 20 bags · 0.10 USDC (test amount)
    • Valid for 15 minutes
    • Payout to a verified Stellar account

    TilcAI does not invent the price: it reproduces what the business published.

  3. 03 / 06 · Owner: TilcAI

    Rules

    TilcAI checks identity, offer, payee, asset, network and budget. The result is allow, block or ask for approval.

    EvaluationState: Evaluated
    • Business and destination verified
    • Within your limit
    • Result: asks for your approval

    “Allow” is eligibility: it neither signs nor pays.

  4. 04 / 06 · Owner: You

    Approval

    You review the exact terms on a secure screen and authorize. Connecting an account, or typing “yes” in a chat, is not a spending authorization.

    Purchase reviewState: Approved
    • Amount: 0.10 USDC
    • Destination: the hardware store, verified
    • Expires with the quote

    Changing the amount or the payee requires approving again.

  5. 05 / 06 · Owner: Payment rail

    Payment

    TilcAI creates an order with an idempotency key and runs a single attempt over the chosen route. Then it checks the asset, amount, payee and result on the network.

    Payment attemptState: Settled
    • One order · one attempt
    • Route: USDC from Fuji to Stellar (CCTP)
    • Evidence: source and destination hash

    An uncertain result is reconciled; the payment is not blindly repeated.

  6. 06 / 06 · Owner: Business and TilcAI

    Two receipts

    Buyer and business see the same order state. The payment receipt arrives when it settles; the business records the pick-up confirmation separately.

    Operation evidenceState: Closed or being followed
    • Payment receipt with testnet links
    • Pick-up confirmation from the business
    • The same orderId for both

    Paid does not mean delivered.

PAYMENT ROUTES

The business is paid in
USDC on Stellar.

TilcAI picks one route per order and never charges twice. They serve different situations: already holding USDC on Stellar, or holding it on another network.

  • One route per order
  • CCTP verified on testnet
  • Same destination
BuyerPays in USDC
TilcAISelects one route per order
✧ Analyzes the route
BusinessReceives USDC on Stellar
  1. 01Pay in USDCFrom a supported network
  2. 02TilcAI routesOne route per order
  3. 03It is confirmedWith network evidence
  4. 04Business is paidUSDC on Stellar
  • x402Direct on Stellar

    When you already hold USDC on Stellar

    • One network
    • One route per order
    • Isolated test with XLM

    Isolated test

  • CCTP · crosschainUSDC from another network

    When you hold USDC on another network

    • Fuji → Stellar verified
    • Native USDC
    • No gas for the buyer

    Verified on testnet

Same intended destination: the business receives USDC on Stellar.

ROUTE DETAIL

USDC from another network

Pay on your network. TilcAI handles the rest.

CCTP · CrosschainAvalanche Fuji verified on testnetNo gas for the buyer

1. SOURCE NETWORK

Choose the network holding your USDC.

DESTINATION OF THIS ROUTEStellar Testnet✓ Verified with Fuji

Avalanche Fuji → Stellar: technical payment verified on testnet.

2. HOW IT WORKS

CCTP moves your USDC to Stellar in 3 steps.

  1. 01
    Burn on origin

    USDC is retired on the source network.

  2. 02ATTESTATION
    Circle confirms

    The burn is attested.

  3. 03
    Mint on Stellar

    The same USDC is issued on Stellar.

3. DESTINATION

Final destination for this route.

Verified with Fuji
Stellar Testnet

Business USDC

Destination tested on the Avalanche Fuji → Stellar technical route.

Same currency
USDC
Same amount
1:1
Destination
Stellar
TilcAI covers the fees.

You only send USDC from your wallet.

No gas for the buyerTilcAI covers network fees.
With evidenceBurn, attestation and mint.
Same termsSame amount, same currency.

CCTP lab networks

Avalanche Fuji, Ethereum Sepolia, Arbitrum Sepolia, and Base Sepolia are verified in TilcAI. Other networks require their own route test.

What this route does not promise

Explore decisions across three commercial cases.

Compare recipient, amount and approval conditions.

Interactive simulation · no funds moved

Choose a scenario

Test a condition

Request

Two tickets for Wednesday.

Service
Cinema tickets
Quantity
2
Timing
Wednesday
Policy / permission
Recipient
Central Cinema
Allowed
Amount
10.00 USDC
Limit
12.00 USDC
Allowed
Result
Allowed
Result: Cinema. Valid conditions. Can continue. “Can continue” does not confirm a payment or transaction.

User control

A specific task. A limited permission.

You decide what is authorized, how much it can spend and when it expires.

Connecting a wallet enables signing, but does not grant spending permission.

Understand permissions
PERMISSION PREVIEW02 / 03

Within the limit

Terms to review

30 / 50 USDC

Ready for review

The conditions match. It can go to review; this does not authorize or pay.

PayeeAuthorized business
ValidityThis purchase only
02Every purchase is checked against your limit.
It stops when

Three ways into the same infrastructure.

The channel changes, the rules do not: all of them end in the same identity, quote, approval, payment and receipts.

Buyer entrances

  • New person · WhatsApp

    A guided conversation. To buy, a secure link opens the screen where you create your credential and approve. WhatsApp starts the process; it is not a signature.

    Reported by the team

  • Your own assistant · MCP

    You connect TilcAI's tools to your assistant: find a service, ask for a quote, request approval, check an order. Allowing a tool does not grant permission to spend.

    Contract defined

  • Your own application · API

    An authenticated backend uses the REST API. A future SDK would package authentication, types and idempotency, but would not replace the API.

    Available on testnet

The same infrastructure

  1. Identity
  2. Quote
  3. Approval
  4. Payment
  5. Receipts

Assistants

Use the assistant you already work with.

Each client will have its own guide, surface and TilcAI integration status. Configuration depends on the specific application you use.

Selecting an assistant or connecting tools does not grant permission to spend.

TerminalIn preparation

Codex

Codex CLI

MCP tools from your development terminal.

Integration status

  1. Client documentationVerified
  2. Transport and authenticationVerified
  3. TilcAI toolsVerified
  4. Human approval of the purchaseVerified

The pieces behind each operation.

Read the full architecture
  • MCPTools for assistants
  • StellarPayment destination
  • SorobanProgrammable authorization
  • USDCPayment asset
  • x402Direct HTTP payment
  • CCTPUSDC across networks (Circle)
  • OpenZeppelin RelayerSponsored execution

Frequently asked questions

Understand the connection and stay in control.

What works today?

There is one verified technical payment: USDC from Avalanche Fuji to Stellar Testnet with CCTP, with an API, reconciliation and a mode where the buyer pays no gas, independently reproduced. There is also a policy evaluator, shared contracts and this website with its simulation. No real business is connected yet: catalog, quote, order, signed approval and delivery confirmation are still being integrated, so the complete purchase flow is not enabled.

How does a business connect?

You do not need an AI agent or a website. We propose four paths: a managed console, a file or spreadsheet, an API or POS connector, or your own agent. In all of them you keep prices, availability, payout destination and delivery confirmation. These are onboarding proposals: they are tried first with one limited pilot business, on testnet.

Can I pay with any money or on any network?

No. TilcAI moves native USDC between enabled networks with CCTP, and the business is paid in USDC on Stellar. Today Avalanche Fuji, Ethereum Sepolia, Arbitrum Sepolia and Base Sepolia, to Stellar Testnet, are verified; three other networks are in the lab and are enabled one at a time. Other tokens or bolivianos need a conversion and a separate provider that do not exist yet.

Can my agent spend without asking me?

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.

Does the simulation make payments?

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.

What if payment is confirmed but the service is not delivered?

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.

Explore how your agents would buy.

Try the decisions in the simulation, see what works today, or learn how to prepare your business for a pilot.