# Why Your AI Agent Needs a Wallet: USDC and Nanopayments — Harshal Bhangale, Circle

Harshal Bhangale, Circle

[Talk page](https://ai.engineer/talks/xKzU_3riL6s-why-your-ai-agent-needs-wallet-usdc) · [Video](https://www.youtube.com/watch?v=xKzU_3riL6s)

## Why Your AI Agent Needs a Wallet: USDC and Nanopayments

Harshal Bhangale’s World Cup trip demo shows how paid data and services help an agent finish a task. Circle combines wallet spending limits, x402 requests, and fast off-chain confirmation so tiny purchases can proceed without a human approving each one.

### The agent reaches a paywall

[0:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=12s)

An agent can have a capable model, many tools, and elaborate orchestration, then stop at a paid endpoint. Someone has to create an account, enter payment information, or manage an API key before work continues. [Harshal Bhangale](https://www.linkedin.com/in/harshaldbhangale), an engineer on Circle’s Agent Tech product team, opens with this practical reason for bringing a stablecoin company to an AI engineering conference: Circle issues **USDC**, and payment can interrupt an otherwise automated task. [1:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=74s)

![Recording frame at 94 seconds](https://ai.engineer/api/talk-essay-media/a384ce70f5c2c2b042cbebdc67ae2ca032d3f47691a4ea2c4768da3afe7a811c)

Recording frame at 94 seconds

The proposed next step follows a progression from prompts in 2023, to workflows in 2024, to MCPs, skills, and orchestration in 2025. Bhangale expects 2026 to bring agents that purchase the services they need. He cites approximately **$24 million** transacted against paid API endpoints over x402 in the preceding thirty days, with **99% settled in USDC**. These are his adoption figures for that window, rather than a measurement of the entire agent economy.

### x402 puts payment inside the request flow

[2:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=165s)

**x402** gives a paid resource a request-and-retry flow. An agent asks a server for something; the server returns `402 Payment Required` with payment details. The agent signs a payment authorization using its wallet and retries the request to obtain the resource. Payment becomes part of the API interaction, avoiding a detour through a human signup process. [2:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=165s)

![Recording frame at 194 seconds](https://ai.engineer/api/talk-essay-media/3182b74ac5b98117f65b03c67f303296a6194f4c0073be3c18d897aabb23584c)

Recording frame at 194 seconds

That flow fits a different pattern of consumption. A human might buy a subscription and browse a service over time. An agent may need one piece of data, a little compute, or a single inference result while completing a larger task. It can inspect hundreds of pages, then skip the paid endpoint that would have supplied a useful answer. Selling that endpoint’s output in a small increment gives the agent another way to continue.

Two changes have to meet:

- **Buyer behavior:** Agents purchase small amounts at high frequency. Payment overhead repeats with every call, so both cost and latency matter.
- **Seller packaging:** A merchant can sell a subset of its data instead of requiring a subscription. Bhangale’s example is a ten-cent purchase for one piece of data, with repeated API calls producing repeated small payments.

Bhangale uses a roughly 3% card fee on a one-cent transaction to illustrate the mismatch. A percentage alone does not explain the full economics; Circle’s supplied [Nanopayments deep dive](https://www.circle.com/blog/a-deep-dive-into-circle-nanopayments-gas-free-usdc-transfers) also identifies fixed fees, settlement latency, and operational overhead. The target is payment that works at the rhythm of API calls: real-time, low-cost, programmable, and always available. **Circle Agent Stack** connects those requirements.

### Two agents plan the same World Cup trip

[6:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=372s)

After some terminal-window wrangling, the demo puts two **Claude Code** sessions side by side. One is a regular session; the other has a funded Circle agent wallet and can pay for premium content. Both receive the same assignment: plan Bhangale’s trip to the FIFA World Cup final. [7:06](https://www.youtube.com/watch?v=xKzU_3riL6s&t=426s)

The task crosses several kinds of information. It asks for flights, hotels, and logistics; Argentina’s chances of reaching the final and its possible opponent; secondary-market ticket prices; and practical advice from people who have visited the stadium. The requested output goes beyond research: email the summary, then, if possible, call and brief him. A six-to-eight-minute instruction keeps the demonstration moving.

Both sessions begin working. The regular session launches subagents and researches hotels and flights. The wallet-equipped session purchases premium information. One paid API request carries a **fifteen-cent maximum**; another queries Polymarket data through a provider and parses the results under a spending limit. Payment becomes another step in collecting the trip’s inputs.

The spending controls belong in the wallet. Approving every one-cent, five-cent, or ten-cent purchase would turn a fast agent into a queue of human interruptions. Instead, the owner sets limits and the wallet enforces them while the agent chooses individual purchases. A maximum for a request and a session or daily cap control different scopes: permitting one small purchase does not grant an unlimited budget. [9:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=553s)

### Research finishes; delivery exposes the difference

[12:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=743s)

The first clear divergence appears at email delivery. The regular session can add a draft to Bhangale’s logged-in Gmail account, but cannot send it. It eventually returns highlights in the terminal and acknowledges that it cannot place a phone call. The wallet-equipped session can pay a provider to send the email and arrange the call. In this setup, buying a service turns a requested action into something the agent can complete; the comparison does not establish that every agent without a wallet lacks email or telephone tools. [12:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=743s)

The received email carries the research out of the terminal and into Bhangale’s inbox. After briefly opening an older message, he finds the new one and describes its stadium directions, maps, ticket information, and advice drawn from Reddit. One session has prepared material it cannot deliver; the other has delivered a trip brief through a purchased service.

The phone call takes longer. Bhangale notes that it can take a few minutes to arrive and returns to the slides while waiting. Payment confirmation and service delivery have separate clocks: authorizing a purchase quickly does not make the purchased service instantaneous.

### Gas and shared block space remain bottlenecks

[15:57](https://www.youtube.com/watch?v=xKzU_3riL6s&t=957s)

A blockchain makes programmable transfers possible, but settling every tiny purchase separately creates another cost problem. Gas can consume a substantial fraction of a small payment. It also serves a purpose: charging for transactions discourages network spam and abuse. Removing that expense from each API purchase requires changing how payments reach the chain. [15:57](https://www.youtube.com/watch?v=xKzU_3riL6s&t=957s)

![Recording frame at 1030 seconds](https://ai.engineer/api/talk-essay-media/20145888cd5ca58080b9ecedff99682bb24564059b38ead43617c05db66c7b1f)

Recording frame at 1030 seconds

Shared block space creates a timing problem as well. Agent payments compete with other blockchain uses, so congestion can make latency unpredictable and degrade performance under load. **Nanopayments**, built on Circle’s **Gateway**, is introduced as a layer for sub-cent transactions, gas-free payment for the seller, and cross-chain operation. The aim is to keep each resource request from waiting on its own blockchain settlement.

Then the explanation is interrupted by the call. The synthetic phone agent begins briefing Bhangale on the World Cup trip and suggests nonstop flights from SFO to EWR or JFK. He asks how to reach the stadium from his hotel. The agent responds with NJ Transit to Secaucus Junction, followed by the Meadowlands rail spur to the stadium. These are demonstration outputs rather than verified travel guidance; their significance here is that the purchased calling service supports a follow-up conversation about the researched task. [17:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1044s)

Bhangale closes the call by saying he will read the rest in his email. The assignment has moved through research, paid data access, email delivery, and a spoken exchange. The wallet supplies the means to purchase missing services; those services perform the delivery and conversation.

### Confirm purchases immediately; settle them later in batches

[18:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1083s)

The mechanism starts with funding. Circle works with providers that convert US dollars into USDC; the wallet’s funds can then be deposited into a smart contract. For an individual purchase, the agent signs an **off-chain authorization** naming the recipient address and the amount. That signature permits a particular payment without requiring the agent to submit a separate on-chain transaction at that moment. [18:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1113s)

The merchant’s server relays the authorization to Circle. Bhangale describes confirmation within a few hundred milliseconds: the merchant learns that the buyer has funds and can release the requested resource. What does the merchant wait for before supplying the data? The diagram follows the authorization through confirmation to delivery. Circle’s confirmation lets the resource request proceed without waiting for a separate blockchain transaction for that purchase.

Circle’s supplied [technical deep dive](https://www.circle.com/blog/a-deep-dive-into-circle-nanopayments-gas-free-usdc-transfers) fills in the later settlement step. Nanopayments checks the authorization against the available balance, deducts the off-chain amount, and confirms to the merchant. Thousands of signed authorizations are then batched, verified in a Trusted Execution Environment, and periodically settled on-chain. Gas remains at the batch level. Fast confirmation depends on Circle’s verification service and the TEE-based batching design, while the chain supplies eventual settlement.

The closing stack separates three jobs:

- **Agent wallets:** Hold funds and enforce the owner’s spending limits while the agent makes individual purchases.
- **Merchant integration:** Wrap endpoints and resources with payment handling using Circle’s SDKs, so sellers can charge for access.
- **USDC and Nanopayments:** Carry value and provide the sub-second payment path beneath those interactions, avoiding separate on-chain settlement for every tiny request.

For agent builders, Bhangale’s closing invitation is to visit `agents.circle.com`, equip an agent with a wallet, and try purchasing services such as phone calls. For merchants, the [Nanopayments documentation](https://developers.circle.com/gateway/nanopayments) explains the buyer and seller integration paths. Its signature requirement matters when choosing a wallet: Nanopayments and x402 batch settlement require externally owned account (EOA) signatures and do not support ERC-1271 smart-contract signature validation. [20:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1203s)

What the merchant waits for
Funding precedes purchases. The merchant relays a signed authorization to Circle and releases the resource after confirmation, without settling each purchase separately on-chain.
- Funded USDC wallet — Funds are deposited into a smart contract before purchases.
- Agent signs authorization — The signature specifies a recipient address and payment amount.
- Merchant server — Relays the signed authorization to Circle.
- Circle confirmation — Confirms funds within a few hundred milliseconds in the described flow.
- Resource delivered — The merchant supplies the requested resource to the agent.
- Funded USDC wallet → Agent signs authorization (Fund first, then authorize purchases)
- Agent signs authorization → Merchant server (Signed payment authorization)
- Merchant server → Circle confirmation (Relay for confirmation)
- Circle confirmation → Merchant server (Confirm available funds)
- Merchant server → Resource delivered (Release after confirmation)

## Key takeaways

- x402 makes paid access a request-and-retry interaction: the server supplies payment details and the agent signs an authorization to obtain the resource.
- Wallet-enforced spending limits let an agent make small purchases without asking a human to approve every transaction.
- In the World Cup demo, purchased services changed the result from a Gmail draft and terminal highlights to a delivered email and a phone conversation.
- Nanopayments separates fast merchant confirmation from later batch settlement, addressing per-payment gas costs and unpredictable shared-block-space latency.

## Resources

- [A Deep Dive into Circle Nanopayments: Gas-Free USDC Transfers](https://www.circle.com/blog/a-deep-dive-into-circle-nanopayments-gas-free-usdc-transfers) — Explains balance deductions, asynchronous batch settlement, gas at the batch level, and the Trusted Execution Environment used to verify authorizations.
- [Circle Gateway Nanopayments documentation](https://developers.circle.com/gateway/nanopayments) — Buyer and seller integration guidance. Nanopayments requires EOA signatures and does not support ERC-1271 smart-contract signature validation.
- [ERC-3009: Transfer With Authorization](https://eips.ethereum.org/EIPS/eip-3009) — Develops the signed-transfer mechanism identified in Circle’s deep dive, including recipient, amount, validity window, and unique nonce fields.

## Related talks

- [When AI Agents Pay and Sellers Monetize: Building x402 Apps on AWS — Anil Nadiminti, AWS](https://ai.engineer/talks/qTZirYu9pr0-when-ai-agents-pay-sellers-monetize-building) — Continues the implementation topic of connecting agent payments to merchant endpoints.
- [x402 isn’t good (yet) — Jan Curn, Apify](https://ai.engineer/talks/h6mi88VrPtQ-x402-isnt-good-yet-jan-curn-apify) — Offers a contrasting discussion of the payment protocol introduced here.
- [Building an AI assistant that makes phone calls](https://ai.engineer/talks/idDnpGqJd80-building-ai-assistant-that-makes-phone-calls) — Explores the calling capability that the trip-planning agent purchases.

## Slides

### Why Your AI Agent Needs a Wallet

AI agents can stall at paywalls or when they need to pay, requiring a person to create an account or manage API keys. The talk explores USDC and nanopayments in the agentic economy.

[0:34](https://www.youtube.com/watch?v=xKzU_3riL6s&t=34s) [Circle title slide introducing the agentic economy, USDC, and nanopayments.](https://assets.ai.engineer/sites/aiecode2025/sha256/a8d402aa34ae29f13d9a50f8d85abf296fb72fe6883bed79b0e02fc800b4d69e.webp)

CIRCLE

Why Your AI Agent Needs a Wallet: Agentic economy with USDC and Nanopayments

### Speaker

Harshal Bhangale is a staff software engineer on Circle’s agentic product team.

[1:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=98s) [Speaker slide identifying Harshal Bhangale as Staff Software Engineer, with his portrait.](https://assets.ai.engineer/sites/aiecode2025/sha256/c1fd4e93607f8a8ba4e6573cca9dd049519f8471268398d87c860536d0d24e69.webp)

Speaker

Harshal Bhangale
Staff Software Engineer

### Agentic economy is already here

Bhangale traces a path from prompts in 2023 to workflows and orchestration, then predicts that 2026 is when agents start paying for services.

[1:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=103s) [Timeline from prompts in 2023 through workflows, orchestration, and transactions in 2026.](https://assets.ai.engineer/sites/aiecode2025/sha256/3c52964fa68bd80f091cab1b2b3c2c2ece81072fcd58ac32585af0ad148f7bcb.webp)

Agentic economy is already here

2023 - Prompt
LLMs & RAG

2024 - Workflow
LangChain & LangGraph

2025 - Orchestration
MCP & Skills

2026 - Transaction
x402 & MPP

CIRCLE 3

### Early traction in agent-driven transactions

The slide reports $24M+ in x402 volume in the 30 days through June 30, 2026, with 98.8% settled in USDC. It also cites $5T in agentic commerce by 2030.

[2:20](https://www.youtube.com/watch?v=xKzU_3riL6s&t=140s) [Slide reports over $24 million in 30-day x402 volume, 98.8% settled in USDC, and a $5 trillion agentic commerce projection for 2030.](https://assets.ai.engineer/sites/aiecode2025/sha256/698d6fc6cfa4c6382918715768f52dbe3552b14464201ded75980eb6d5e72ea1.webp)

Early traction in agent-driven transactions

$24M+
x402 volume
last 30 days as of June 30, 2026¹

98.8%
settled in USDC
as of June 30,, 2026²

$5T
in agentic commerce
by 2030³

x402.org
Dune
McKinsey

CIRCLE 4

### Agents can do the work. They get stuck at payments.

Bhangale argues that human-oriented account setup and card authorization impede agents. His fee example shows the problem for small payments: a $0.30 fee overwhelms a $0.002 API call.

[3:18](https://www.youtube.com/watch?v=xKzU_3riL6s&t=198s) [Slide describes account setup, human payment authorization, and transaction fees as barriers to agent payments, alongside a CAPTCHA illustration.](https://assets.ai.engineer/sites/aiecode2025/sha256/c67a0afc3a12972e6dc7bbbfcae2fca2100fb55bc1c1405bce302d8c2092db89.webp)

Agents can do the work.
They get stuck at payments.

Create accounts, passwords, API keys, and more, which machines can’t do

Credit cards today require human to sign or authorize every transaction

Transaction fees not designed for high frequency, sub-cent transactions. If an agent needs to pay $0.002 for an API call, a $0.30 fee kills the model.

I'm not a robot
reCAPTCHA
Privacy - Terms

CIRCLE 5

### Side-by-side Claude Code sessions

The demo pairs a regular Claude Code session with one equipped with a funded Circle agent wallet for paying for premium content. The presenter plans to give both the same World Cup trip-planning task.

[7:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=420s) [Two Claude Code terminal sessions are open side by side.](https://assets.ai.engineer/sites/aiecode2025/sha256/e056b9016030bf7dd3dbe8d5eac1ecdbbf6617e22afb4a79c7dd05c8b3c7b198.webp)

Interface text:
Left session:
Claude Code v2.1.198
Sonnet 5 with low effort · Claude Enterprise
~/newsletter-demo/vanilla-claude
4 MCP servers need authentication · run /mcp

auto mode on (shift+tab to cycle) · [illegible] for agents

Right session:
Claude Code v2.1.198
Sonnet 5 with low effort · Claude Enterprise
~/newsletter-demo/claude-with-circle-wallets
4 MCP servers need authentication · run /mcp

auto mode on (shift+tab to cycle) · [illegible] for agents
Enable Automatic Updates?

### Flight and hotel research

The vanilla agent splits the World Cup trip into flight and hotel research; hotels finish while flights are still running. Beside it, the wallet-equipped session issues paid API calls with per-call maximums.

[10:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=608s) [A terminal shows a World Cup trip research request and parallel flight and hotel tasks.](https://assets.ai.engineer/sites/aiecode2025/sha256/c95b33fba70a227cc30c35d3ebd7093d08485cea409b18ccfece02af7675c11b.webp)

Research current, sourced data for a trip to the 2026 FIFA World Cup Final on July 19, 2026 at MetLife Stadium, East Rutherford NJ. Flying from Bay Area (SFO/OAK/SJC) to NYC area (JFK/LGA/EWR), July 17 out / July 20 back.

Use web search (free public sources only, no paid APIs). For every number give the source name and today's date (2026-07-02) or note if data is from a slightly earlier cached date.

1. FLIGHTS: For realistic nonstop pairs among {SFO,OAK,SJC} x {JFK,LGA,EWR}, identify which airlines fly nonstop each route, and get a rough current round-trip economy fare for July 17→20, 2026 (check Google Flights/Kayak/airline sites via search). Also get: recent on-time performance / delay-cancellation stats for each origin and destination airport (FlightAware/BTS/FAA sources), and the July weather outlook for NYC-area airports around July 19. Recommend the single best pairing with justification. Label anything not independently verifiable as "UNVERIFIED — estimate".

2. HOTELS: Find 5 real hotel options near East Rutherford NJ / Manhattan for July 17-20, 2026. Split into "walkable/near stadium" (e.g. Rutherford, Secaucus, Carlstadt) vs "Manhattan with easy transit". For each give: exact street address, star rating + review count (from Google/TripAdvisor), current nightly rate estimate with source+date, and distance in miles from MetLife Stadium (40.8135,-74.0745). Provide a Google Maps link (format: https://www.google.com/maps/search/?api=1&query=<address URL-encoded>) for each.

Report back concisely with all sourced facts organized under headers "FLIGHTS" and "HOTELS". Include a short list of sources with links at the end.

I'll research this using web search directly.
I'll dispatch two parallel research forks for flights and hotels to keep this fast.
2 background agents launched
  flights-research: Research flights for World Cup final trip
  hotels-research: Research hotels for World Cup final trip
Both research forks are running in the background — one on flights (routes, airlines, fares, on-time stats, weather), one on hotels (5 options with addresses, ratings, rates, distances, map links). I'll compile the final report once both return.
Hotels research is done. Waiting on flights before compiling the final report.
Waiting for 1 background agent to finish

Right-hand session:
Read 922 lines
Read(/tmp/polymarket.json)
  Read 1083 lines
Read(/tmp/hotels_stadium.json)
  Read 8 lines
Read(/tmp/hotels_manhattan.json)
  Read 8 lines
Bash(source /tmp/wallet.env
circle services pay "https://stableenrich.dev/api/google-maps/text-search/full" --address "$WALLET" --chain BASE -X POST -d '{"textQuery":"hotels near MetLife Stadium East Rutherford NJ","maxResultCount":10,"locationBias":{"circle":{"center":{"latitude":40.8135,"longitude":-74.0745},"radius":8000}},"minRating":4}' --max-amount 0.15 -o json > /tmp/hotels_stadium.json 2>&1
echo done1
circle services pay "https://stableenrich.dev/api/google-maps/text-search/full" --address "$WALLET" --chain BASE -X POST -d '{"textQuery":"hotels in Manhattan near Penn Station New York","maxResultCount":10,"minRating":4}' --max-amount 0.15 -o json > /tmp/hotels_manhattan.json 2>&1
echo done2)
  Running in the background
Bash(source /tmp/wallet.env
circle services pay "https://nano.blockrun.ai/api/v1/pm/kalshi/markets" --address "$WALLET" --chain MATIC -X GET -d '{"search":"World Cup winner","limit":100,"sort":"volume"}' --max-amount 0.01 -o json > /tmp/kalshi2.json 2>&1
echo done)
  Running in the background
Bash(source /tmp/wallet.env
circle services pay "https://nano.blockrun.ai/api/v1/pm/polymarket/markets" --address "$WALLET" --chain MATIC -X GET -d '{"search":"2026 World Cup winner","limit":100,"sort":"volume"}' --max-amount 0.01 -o json > /tmp/polymarket2.json 2>&1
echo done)
  Running in the background
Read(/tmp/delays_KSFO.json)
  Read 19 lines
Read(/tmp/flights.json)
  Read 16 lines
Read(/tmp/tickets.json)
  Read 16 lines
Read(/tmp/reddit.json)
  Read 105 lines
Read(/tmp/clearbag.json)
Bash(source /tmp/wallet.env
circle services inspect "https://api.aisa.one/apis/v2/perplexity/sonar-pro" -o json 2>&1 | head -60
echo "---delays---"
circle services inspect "https://stabletravel.dev/api/flightaware/airports/id/delays" -o json 2>&1 | head -40)
{
  "data": {
    "status": "payable",
    "httpStatus": 402,

Interface text:
Claude Code v2.1.198
Sonnet 5 with low effort · Claude Enterprise
~/newsletter-demo/vanilla-claude
4 MCP servers need authentication · run /mcp
Spelunking… (2s · ↓ 37.1k tokens · thinking with low effort)
Tip: You have 12 plugins you haven't used in a while. They still add startup and context cost — review them with /plugin
Research flights and hotels for World Cup Final trip
>> auto mode on (shift+tab to cycle) · + for agents · ↓ to manage
main
general-purpose  Research flights and hotels for World Cup Final trip
flights-research  Compiling hotel details and distances  idle
general-purpose  Searching Reddit for scam warnings
1 new message (ctrl+End)
Enable Automatic Updates?

### Hotel research results

The vanilla agent compares hotels near MetLife Stadium with Manhattan options: closer rooms offer game-day convenience, while Manhattan adds a roughly 45–60 minute transit trip. Its displayed Final-weekend rates are unverified estimates.

[10:18](https://www.youtube.com/watch?v=xKzU_3riL6s&t=618s) [A terminal lists hotels near the stadium and in Manhattan, with ratings, distances and estimated rates.](https://assets.ai.engineer/sites/aiecode2025/sha256/7f9a86eaa9767e82f8fa58b8e10052e5fbc9395f9a32f5dab090004dcbd0e4a1.webp)

- Rating: ~3.5★ (mixed; 5/5 on TripAdvisor per most recent reviews, 6.0/10 on Expedia) — reviews mixed
- Rate: UNVERIFIED — estimate: $400-$900+/night for World Cup Final dates (base rates listed from $99 off-peak; expect major surge)
- Distance: ~0.3 miles from MetLife Stadium
- Maps: https://www.google.com/maps/search/?api=1&query=2%20Meadowlands%20Plaza%2C%20East%20Rutherford%2C%20NJ%2007073

2. SpringHill Suites East Rutherford Meadowlands/Carlstadt
- Address: 192 Paterson Plank Road, Carlstadt, NJ 07072
- Rating: 3/5 TripAdvisor (#3 of 4 hotels in Carlstadt)
- Rate: UNVERIFIED — estimate: $350-$700+/night for Final weekend
- Distance: ~1.2 miles from MetLife Stadium
- Maps: https://www.google.com/maps/search/?api=1&query=192%20Paterson%20Plank%20Road%2C%20Carlstadt%2C%20NJ%2007072

3. Renaissance Meadowlands Hotel
- Address: 801 Rutherford Avenue, Rutherford, NJ 07070
- Rating: 4/5 TripAdvisor (#1 of 2 in Rutherford), 8.3/10 Booking.com (235 reviews)
- Rate: UNVERIFIED — estimate: $400-$800+/night for Final weekend
- Distance: ~3.2 miles from MetLife Stadium
- Maps: https://www.google.com/maps/search/?api=1&query=801%20Rutherford%20Avenue%2C%20Rutherford%2C%20NJ%2007070

Manhattan with easy transit (NJ Transit/train to MetLife area)

4. Hilton New York Times Square
- Address: 234 W 42nd St, New York, NY 10036
- Rating: 4/5 TripAdvisor (#292 of 522 in NYC; TripAdvisor Hall of Fame 5 years running), 478 rooms
- Rate: UNVERIFIED — estimate: $500-$1,000+/night for Final weekend (base rates typically $300-450 off-peak)
- Distance: ~9 miles from MetLife Stadium; near Port Authority for NJ Transit bus to Meadowlands
- Maps: https://www.google.com/maps/search/?api=1&query=234%20W%2042nd%20St%2C%20New%20York%2C%20NY%2010036

5. YOTEL New York Times Square
- Address: 570 Tenth Avenue, New York, NY 10036
- Rating: 4/5 TripAdvisor (7.4/10 Booking.com, #431 of 522 in NYC)
- Rate: UNVERIFIED — estimate: $400-$800+/night for Final weekend (base ~$135-250 off-peak per MakeMyTrip)
- Distance: ~9.3 miles from MetLife Stadium; 2 blocks from Port Authority Bus Terminal (NJ Transit buses run direct to Meadowlands on event days)
- Maps: https://www.google.com/maps/search/?api=1&query=570%20Tenth%20Avenue%2C%20New%20York%2C%20NY%2010036

Recommendation: For game-day convenience, the NJ-side hotels (World of Blue, SpringHill Suites) win on distance but expect the steepest surge pricing and limited inventory as the closest options. Manhattan near Port Authority (YOTEL, Hilton Times Square) gives more room supply and easier flight/subway connectivity, at the cost of a ~45-60 min NJ Transit bus/rail trip to the stadium on event day.

Sources:
- Tripadvisor: World of Blue
- Tripadvisor: SpringHill Suites Carlstadt
- Tripadvisor: Renaissance Meadowlands
- Tripadvisor: Hilton New York Times Square
- Tripadvisor: YOTEL New York Times Square
- Travel And Tour World: NYC hotel occupancy/rate surge

Bottom line: Fly SFO-EWR on United for the shortest/most reliable nonstop option and closest airport to the stadium; book hotels now given the confirmed surge pricing pattern (228%+ rate increases already observed for earlier MetLife matches) — waiting will likely make Final-weekend rooms both pricier and scarcer.

Interface text:
Read 922 lines
Read(/tmp/polymarket.json) — Read 1083 lines
Read(/tmp/hotels_stadium.json) — Read 8 lines
Read(/tmp/hotels_manhattan.json) — Read 8 lines
Bash(source /tmp/wallet.env
  circle services pay "https://stableenrich.dev/api/google-maps/text-search/full" --address "$WALLET" --chain BASE -X POST -d '{"textQuery":"hotels near MetLife Stadium East Rutherford NJ","maxResultCount":10,"locationBias":{"circle":{"center":{"latitude":40.8135,"longitude":-74.0745},"radius":8000}},"minRating":4}' --max-amount 0.15 -o json > /tmp/hotels_stadium.json 2>&1
  echo done1
  circle services pay "https://stableenrich.dev/api/google-maps/text-search/full" --address "$WALLET" --chain BASE -X POST -d '{"textQuery":"hotels in Manhattan near Penn Station New York","maxResultCount":10,"minRating":4}' --max-amount 0.15 -o json > /tmp/hotels_manhattan.json 2>&1
  echo done2)
Running in the background (↓ to manage)
Bash(source /tmp/wallet.env
  circle services pay "https://nano.blockrun.ai/api/v1/pm/kalshi/markets" --address "$WALLET" --chain MATIC -X GET -d '{"search":"World Cup winner","limit":100,"sort":"volume"}' --max-amount 0.01 -o json > /tmp/kalshi2.json 2>&1
  echo done)
Running in the background (↓ to manage)
Bash(source /tmp/wallet.env
  circle services pay "https://nano.blockrun.ai/api/v1/pm/polymarket/markets" --address "$WALLET" --chain MATIC -X GET -d '{"search":"2026 World Cup winner","limit":100,"sort":"volume"}' --max-amount 0.01 -o json > /tmp/polymarket2.json 2>&1
  echo done)
Running in the background (↓ to manage)
Read(/tmp/delays_KSFO.json) — Read 19 lines
Read(/tmp/flights.json) — Read 16 lines
Read(/tmp/tickets.json) — Read 16 lines
Read(/tmp/reddit.json) — Read 105 lines
Read(/tmp/clearbag.json)
Bash(source /tmp/wallet.env
  circle services inspect "https://api.aisa.one/apis/v2/perplexity/sonar-pro" -o json 2>&1 | head -60
  echo "---delays---"
  circle services inspect "https://stabletravel.dev/api/flightaware/airports/id/delays" -o json 2>&1 | head -40)
"data": {
  "status": "payable",
2 new messages (ctrl+End) ↓
auto mode on (shift+tab to cycle) · esc to interrupt · ← for agents · ↓ to manage
main
general-purpose — Research flights and hotels for World Cup Final trip
flights-research — Compiling hotel details and distances — idle
Enable Automatic Updates?

### Flights and hotels research

The left agent retries its flight research after the first flight agent returns hotel content. On the right, another agent finishes background lookups and begins composing a travel plan.

[11:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=695s) [Split-screen agent demo showing a travel research task, a flight research retry, and background lookup progress.](https://assets.ai.engineer/sites/aiecode2025/sha256/b5fbbaa0a4de788de79cd288af4a46f8560161189106b51149f5004534fbd73f.webp)

Research current, sourced data for a trip to the 2026 FIFA World Cup Final on July 19, 2026 at MetLife Stadium, East Rutherford NJ. Flying from Bay Area (SFO/OAK/SJC) to NYC area (JFK/LGA/EWR), July 17 out / July 20 back.

Use web search (free public sources only, no paid APIs). For every number give the source name and today's date (2026-07-02) or note if data is from a slightly earlier cached date.

1. FLIGHTS: For realistic nonstop pairs among {SFO,OAK,SJC} x {JFK,LGA,EWR}, identify which airlines fly nonstop each route, and get a rough current round-trip economy fare for July 17-20, 2026 (check Google Flights/Kayak/airline sites via search). Also get: recent on-time performance / delay-cancellation stats for each origin and destination airport (FlightAware/BTS/FAA sources), and the July weather outlook for NYC-area airports around July 19. Recommend the single best pairing with justification. Label anything not independently verifiable as "UNVERIFIED — estimate".

2. HOTELS: Find 5 real hotel options near East Rutherford NJ / Manhattan for July 17-20, 2026. Split into "walkable/near stadium" (e.g. Rutherford, Secaucus, Carlstadt) vs "Manhattan with easy transit". For each give: exact street address, star rating + review count (from Google/TripAdvisor), current nightly rate estimate with source+date, and distance in miles from MetLife Stadium (40.8135,-74.0745). Provide a Google Maps link (format: https://www.google.com/maps/search/?api=1&query=<address URL-encoded>) for each.

Report back concisely with all sourced facts organized under headers "FLIGHTS" and "HOTELS". Include a short list of sources with links at the end.

I'll research this using web search directly.
I'll dispatch two parallel research forks for flights and hotels to keep this fast.

2 background agents launched
- flights-research: Research flights for World Cup final trip
- hotels-research: Research hotels for World Cup final trip

Both research forks are running in the background — one on flights (routes, airlines, fares, on-time stats, weather), one on hotels (5 options with addresses, ratings, rates, distances, map links). I'll compile the final report once both return.

Hotels research is done. Waiting on flights before compiling the final report.

The flights agent returned hotel content by mistake (likely context bleed). Let me re-run a fresh flights research task to get the correct data.

fork(Research flights for World Cup final trip, redo)

Flights v2 research is running in the background now. I'll wait for it before compiling the final combined report.

Waiting for 1 background agent to finish

Right pane:
USA | 4.2 2216 | {'latitude': 40.7522536, 'longitude': -73.9950612}
Read(/tmp/delays_KJFK.json)
  Read 19 lines
Read(/tmp/secaucus.json)
  Read 8 lines

Background command "Get delay stats for SFO, OAK, SJC" completed (exit code 0)
Background command "Get ticket resale price research via Perplexity" completed (exit code 0)
Background command "Get delay stats for JFK, LGA, EWR" completed (exit code 0)
Background command "Get flight fare research via Perplexity" completed (exit code 0)
Background command "Shop for FIFA compliant clear bag" completed (exit code 0)
Background command "Search Reddit for fan tips" completed (exit code 0)
Background command "Get Secaucus Junction station coordinates" completed (exit code 0)
Background command "Retry Kalshi search with tighter terms" completed (exit code 0)
Background command "Retry hotel searches with sufficient max-amount" completed (exit code 0)
Background command "Retry Polymarket search with tighter terms" completed (exit code 0)
Background command "Cross-match World Cup winner markets between venues" completed (exit code 0)
Background command "Fix delay lookups using correct path param" completed (exit code 0)

I'm well past the time budget already — let me lock in what I have, grab the remaining Kalshi/Polymarket winner data and delay stats, then move straight to composing and sending.

Read 2 files, ran 3 shell commands

Background command "Targeted Kalshi queries for World Cup winner and match markets" completed (exit code 0)
Background command "Fix Perplexity calls with required model/messages fields" completed (exit code 0)

Now I have solid data on tickets, flights, and delays. I have enough to compose the plan now — moving straight to writing and sending the email.

Running 4 shell commands...
  $ python3 -c "
    import math
    STAD=(40.8135,-74.0745)
    def d(lat,lon):
      R=3958.8
      dlat=math.radians(lat-STAD[0]); dlon=math.radians(lon-STAD[1])
      a=math.sin(dlat/2)**2+math.cos(math.radians(STAD[0]))*math.cos(math.radians(lat))*math.sin(dlon/2)**2
      return R*2*math.asin(math.sqrt(a))
    hotels=[
    ('Hampton Inn [illegible]

Interface text:
Claude Code v2.1.198
Sonnet 5 with low effort · Claude Enterprise
~/newsletter-demo/vanilla-claude
4 MCP servers need authentication · run /mcp
Spelunking… (27s · ↓ 46.7k tokens)
Tip: You have 12 plugins you haven't used in a while. They still add startup and context cost — review them with /plugin
Research flights and hotels for World Cup Final trip
auto mode on (shift+tab to cycle) · ← for agents · ↓ to manage
main
general-purpose  Research flights and hotels for World Cup Final trip  3m 34s
flights-research-v2  Searching NYC weather and flight delays  idle
Beaming… (4m 4s · ↓ 14.4k tokens)
auto mode on (shift+tab to cycle) · esc to interrupt · ← for agents
Enable Automatic Updates?

### World Cup travel brief

The newly received email combines flight, hotel, transit and ticket recommendations into a $10,600–$19,800 estimate for three nights and one ticket.

[15:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=900s) [An email displays a travel brief with flight, hotel, transit, ticket, and budget recommendations.](https://assets.ai.engineer/sites/aiecode2025/sha256/411b3e60006b5568a276b0d5e2dc9216d1cd8fd382c7f1bc8809e472e9ea3109.webp)

World Cup Final Concierge Brief — MetLife Stadium, July 19

World Cup Final — Travel Brief
MetLife Stadium, East Rutherford NJ · Sunday, July 19, 2026, 3:00 PM
Prepared July 2, 2026 · SFO/OAK/SJC → NYC-area, July 17–20

Book these now

Flight: SFO → EWR nonstop (United/JetBlue territory) — best reliability read, ~$400–$650 RT est.
Hotel: Renaissance Meadowlands Hotel, Rutherford NJ — 1.55 mi from stadium, 4.2★ (1,193 reviews).
Transit: NJ Transit Meadowlands Rail from Secaucus Junction — official match-day shuttle, ~15–20 min.
Ticket: Cat 4 resale currently $2,500–$12,000+; cheapest listed seat $8,311 (StubHub, Section 305).
Total est.: $10,600 – $19,800 for 3 nights, one ticket, flight, transit, food (see Budget table).

1. Flights — Bay Area → NYC

Live reliability pulled from FlightAware (StableTravel), July 2, 2026, ~2:20pm ET:
Airport | Live delay status

Interface text:
Gmail; Ask Gmail; Compose; Inbox 7,155; AI Inbox; Starred; Snoozed; Sent; Drafts 45; Categories; Purchases 6; More; Labels; Confluence 4,611; OTP for TR France; Personal 9.
External; Inbox; Add to Calendar
StableEmail <relay@stableemail.dev>; to me; 11:23 AM (2 minutes ago)
Reply; Forward; Share in chat; 1 of 17,527

### Travel brief: fan reports

The brief uses Reddit fan reports to flag transit costs, early arrival and concession shortages. It also marks betting-market data as unverified after the search returned unrelated results.

[15:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=923s) [The travel brief shows fan reports, practical advice, and the beginning of a ticket section.](https://assets.ai.engineer/sites/aiecode2025/sha256/19a53ab93dbe4630e2a6bf498cfe1b830db8bc359f9f2477e7b730d8a59cc902.webp)

From the match-result data that did come through cleanly: Germany has won both of its most recent tracked knockout matches — beat Ivory Coast 2026-06-20 and beat Ecuador 2026-06-25 — putting them among the sides still alive deep in the bracket as of today. Polymarket per-team World Cup winner odds, 7-day momentum, and buy/sell flow, and the Kalshi/Polymarket side-by-side for the other 5 contenders, could not be retrieved this session (search endpoint returned unrelated markets on every attempt) — UNVERIFIED, needs a follow-up lookup before you rely on it for betting or scheduling decisions.

5. What to expect — fan reports

Live Reddit search, July 2, 2026:

• Transit cost: “Seems like the NJ Transit from HOB is the best option although each ticket costs $98” — u/Delicious_Series_449, r/jerseycity, “Anyone went to Metlife for worldcup?” (Jun 15, 2026)
• Arriving early pays off: “took the bus from port authority at 11 and got to the stadium in 20 mins and getting early to the stadium is important if you want to do activities... They open the gates at 12” — u/PerplexedMythology, r/WorldCup2026Tickets, “Stadium Tips for New York/New Jersey” (Jun 16, 2026)
• VIP concession scarcity: “Trophy Lounge for Brazil v Morocco is out of beer, soda, water, and ice... they can't serve shots” — u/ropps202, r/worldcup, “MetLife Stadium Trophy Lounge VIP is out of everything” (Jun 13, 2026)

Bring: layers (July evening at MetLife can cool off), a clear bag only (see below), a portable charger, and cash for street vendors near the PATH/rail stations. Watch for scalpers near Secaucus Junction claiming to have “extra” tickets — buy only through FIFA official resale.

6. Match ticket & clear bag

Resale ranges via Perplexity/Sonar Pro, citing worldcup.nyc's daily-updated tracker + StubHub/USA Today/NorthJersey, pulled July 2, 2026:

Category | Tracker floor | Real current range

Interface text:
Gmail; Ask Gmail; Compose; Mail; Chat; Meet; Inbox 7,155; AI Inbox; Starred; Snoozed; Sent; Drafts 45; Categories; Purchases 6; More; Labels; Confluence 4,611; OTP for TR France; Personal 9; 1 of 17,527; Reply; Forward; Share in chat; Ask Gemini.

### Gas fee becomes a bottleneck

For a $0.0001 transfer, 2025 average base fees are 537,000% on Ethereum, 4,500% on Base and 1,000% on Solana, before priority fees. Gas also protects networks from spam and abuse.

[15:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=955s) [A table compares gas fees as percentages of small transfers on Ethereum, Base, and Solana.](https://assets.ai.engineer/sites/aiecode2025/sha256/eaa1cafe11a01b63490119d7c1ce9fb57128034f99c8a5853ccd7536d16e0dd8.webp)

Gas fee becomes a bottleneck

At sub-cent denominations, gas fees often exceed the value of the payment itself. This makes individual onchain settlement for every request economically irrational.

2025 Avg. Base Fee*

Transfer Amount (USD) | Ethereum (~$0.5370) | Base (~$0.0045) | Solana (~$0.0010)
$0.01 | 5,370% fee | 45% fee | 10% fee
$0.0001 | 537,000% fee | 4,500% fee | 1,000% fee
$0.000001 | 53,700,000% fee | 450,000% fee | 100,000% fee

But gas is important to protect the network from spam and abuse.

*These calculations are based on the avg. base fee for the applicable chain in 2025. They do not include the priority fee, which transactions often also incur and which may further increase transfer costs significantly.

CIRCLE 10

### Blockchain throughput limitations

Agents share block space with other workloads, making latency unpredictable and performance vulnerable under load, even on high-throughput chains.

[16:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=995s) [Slide lists blockchain throughput constraints and identifies unpredictable latency and degraded performance under load as problems for agents.](https://assets.ai.engineer/sites/aiecode2025/sha256/ef8fb344ac04f5183fa1b4ceb16a5a5462bbefff418a7ff548328e65bb402fa9.webp)

Blockchains have throughput limitations

Traditional blockchains throughput limited by:
• block size
• gas markets
• shared network congestion

Even high-throughput chains:
• Solana (~tens of thousands TPS theoretical)
• Still compete in a shared mempool
• Cannot guarantee consistent capacity for one workload

Problem for agents:
• unpredictable latency
• degraded performance under load

CIRCLE 11

### Circle Gateway Nanopayments

Circle Gateway supports gas-free USDC transfers from $0.000001 and instant liquidity transfers to supported EVM chains. Agents sign off-chain authorizations after funds enter a smart contract; servers relay them to Circle.

[16:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1007s) [Slide presents Nanopayments for sub-cent, gas-free USDC transfers, with crosschain and x402 compatibility.](https://assets.ai.engineer/sites/aiecode2025/sha256/360854c67c79fdcd0cd319aeeacc4a20b386c55d9cfcc9f7d29d45dc162f5853.webp)

Circle Gateway
Nanopayments

The financial rail for agentic economic activity with gas-free USDC transfer

Built for sub-cent transaction sizes
• As low as 1 microcent ($0.000001)
• Also supports regular-size payments

Gas-free
• Transfers are gas-free. Not gas abstracted.

Instantly crosschain
• Liquidity can be instantly transferred to any Gateway-supported EVM chain

X402-compatible
• Compatible with existing x402 v2 integrations
• More protocol support to come

Circle Technology Services, LLC (“CTS”) is a software provider and does not provide regulated financial or advisory services. You are solely responsible for services you provide to users, including obtaining any necessary licenses or approvals and otherwise complying with applicable laws. For additional details, refer to the Circle Developer terms of service

CIRCLE 12

### Get Started

Visit Circle’s agent site to equip an agent with a wallet. The speaker says setup takes a couple of clicks.

[20:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1217s) [Get Started slide with a link to Circle's agents site.](https://assets.ai.engineer/sites/aiecode2025/sha256/1688e425912866a7262c46505c20a886d4dace448f11ae93ffa8db7af4cc35ad.webp)

Get Started

https://agents.circle.com/

CIRCLE 13

### AI Engineer World's Fair

[20:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1243s) [AI Engineer World's Fair title in white on a black background.](https://assets.ai.engineer/sites/aiecode2025/sha256/5cce69006d9faba1eb08528321e22c06abba8aac00ff134def0be8fdae4bb0b1.webp)

AI Engineer
World’s Fair

HTTPS://AI.ENGINEER

## Full transcript

[0:01](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1s) [music]

[0:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=12s) >> Good morning, everyone.

[0:15](https://www.youtube.com/watch?v=xKzU_3riL6s&t=15s) So, um I've had the pleasure of uh

[0:18](https://www.youtube.com/watch?v=xKzU_3riL6s&t=18s) meeting a lot of folks at uh the booth

[0:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=21s) here over the last couple of days, and

[0:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=24s) the interactions have been great, uh but

[0:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=27s) one question kept uh coming up, which

[0:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=29s) was

[0:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=30s) Circle is a stablecoin company. So, why

[0:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=33s) is a stablecoin company at an AI

[0:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=36s) engineering conference?

[0:37](https://www.youtube.com/watch?v=xKzU_3riL6s&t=37s) And well, uh the answer to that is

[0:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=40s) fairly simple,

[0:41](https://www.youtube.com/watch?v=xKzU_3riL6s&t=41s) because

[0:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=42s) Circle issues uh USDC, which is the

[0:46](https://www.youtube.com/watch?v=xKzU_3riL6s&t=46s) world's largest regulated stablecoin.

[0:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=49s) And we've

[0:50](https://www.youtube.com/watch?v=xKzU_3riL6s&t=50s) built over the years expertise in making

[0:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=53s) payments simpler and cheaper.

[0:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=55s) And it turns out that's one of the

[0:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=58s) bottlenecks for your AI agents.

[1:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=60s) So, when you often think about making AI

[1:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=63s) agents smarter, we think about better

[1:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=67s) models,

[1:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=68s) uh more tool calls,

[1:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=70s) complex orchestration,

[1:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=72s) but

[1:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=73s) where your agent actually

[1:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=76s) in practice actually halts is when it

[1:18](https://www.youtube.com/watch?v=xKzU_3riL6s&t=78s) hits a paywall or when it has to pay for

[1:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=81s) something.

[1:22](https://www.youtube.com/watch?v=xKzU_3riL6s&t=82s) Then you have to step in, either create

[1:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=84s) an account, sign up, or, you know,

[1:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=87s) manage API keys.

[1:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=89s) So, that's where uh the limitation is,

[1:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=93s) and that's the gap that I want to talk

[1:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=95s) about today.

[1:37](https://www.youtube.com/watch?v=xKzU_3riL6s&t=97s) So,

[1:39](https://www.youtube.com/watch?v=xKzU_3riL6s&t=99s) yeah, I'm Harshal, and I'm an engineer

[1:41](https://www.youtube.com/watch?v=xKzU_3riL6s&t=101s) on the agentic product team at Circle.

[1:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=105s) So, let's sort of take a step back and

[1:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=108s) see how we got here.

[1:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=109s) We believe that the agentic economy is

[1:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=111s) already here.

[1:52](https://www.youtube.com/watch?v=xKzU_3riL6s&t=112s) So,

[1:54](https://www.youtube.com/watch?v=xKzU_3riL6s&t=114s) how are uh

[1:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=115s) you know, uh

[1:56](https://www.youtube.com/watch?v=xKzU_3riL6s&t=116s) we In 2023 we interacted with agents via

[2:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=120s) like prompts, uh your ChatGPT and stuff

[2:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=123s) like that. We got a little bit better.

[2:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=125s) In 2024 we built workflows.

[2:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=127s) 2025 was all about MCPs, skills, and

[2:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=130s) orchestration.

[2:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=132s) And we believe this year, 2026, is when

[2:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=134s) agents actually start paying for

[2:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=136s) services that they want.

[2:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=139s) And the signals are promising.

[2:22](https://www.youtube.com/watch?v=xKzU_3riL6s&t=142s) Just in the last 30 days,

[2:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=145s) uh agents have transacted with paid API

[2:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=149s) endpoints,

[2:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=150s) uh and the volume is about like $24

[2:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=152s) million. Uh

[2:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=153s) over X102.

[2:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=155s) And 99% of it has been settled in USDC.

[2:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=160s) While this number may look small in

[2:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=162s) terms of volume in the broader

[2:44](https://www.youtube.com/watch?v=xKzU_3riL6s&t=164s) landscape,

[2:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=165s) it's only about to get larger.

[2:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=168s) So, what is X102? Um essentially, X102

[2:52](https://www.youtube.com/watch?v=xKzU_3riL6s&t=172s) is

[2:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=173s) a way where agents can uh pay for their

[2:56](https://www.youtube.com/watch?v=xKzU_3riL6s&t=176s) the resources that they want because

[2:59](https://www.youtube.com/watch?v=xKzU_3riL6s&t=179s) the server essentially returns a 402

[3:01](https://www.youtube.com/watch?v=xKzU_3riL6s&t=181s) header

[3:02](https://www.youtube.com/watch?v=xKzU_3riL6s&t=182s) and with the details of how they want

[3:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=185s) the payment to

[3:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=187s) proceed. And then the agent just signs

[3:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=190s) um an authorization from the crypto

[3:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=192s) wallet and then pays for the resource

[3:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=194s) and retries the request again. So,

[3:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=196s) that's

[3:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=197s) in X102 in a nutshell and we'll see that

[3:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=199s) in action in a live demo.

[3:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=201s) But then, the question is

[3:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=204s) why do the traditional payment rails not

[3:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=207s) work and why do the agents get stuck?

[3:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=210s) So,

[3:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=211s) the answer is simple, uh because for the

[3:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=213s) last 30 years we built the internet

[3:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=216s) around one customer

[3:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=218s) and that was humans.

[3:39](https://www.youtube.com/watch?v=xKzU_3riL6s&t=219s) Right? Um so, we built payment schemes,

[3:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=222s) uh monetization strategies, all catered

[3:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=225s) towards how humans interacted. So, you

[3:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=228s) had your sign-up flows, add your credit

[3:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=231s) card, uh put in your information, and

[3:54](https://www.youtube.com/watch?v=xKzU_3riL6s&t=234s) manage your API keys, but agents just

[3:56](https://www.youtube.com/watch?v=xKzU_3riL6s&t=236s) don't function that way.

[3:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=238s) Agents

[3:59](https://www.youtube.com/watch?v=xKzU_3riL6s&t=239s) want to like come in and grab that piece

[4:01](https://www.youtube.com/watch?v=xKzU_3riL6s&t=241s) of data, resource, compute, inference,

[4:04](https://www.youtube.com/watch?v=xKzU_3riL6s&t=244s) whatever, and just

[4:06](https://www.youtube.com/watch?v=xKzU_3riL6s&t=246s) uh you know, and they have the ability

[4:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=248s) to even like consume knowledge at a

[4:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=250s) scale that humans just cannot.

[4:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=252s) I'm sure like you have seen sessions

[4:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=254s) where it's able to like just scrape

[4:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=256s) through hundreds of web pages, and um

[4:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=259s) then it just like stalls because it

[4:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=261s) can't like reach a particular endpoint,

[4:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=263s) and it skips over it.

[4:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=265s) So,

[4:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=267s) then you could think, "Oh, yeah, just

[4:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=269s) give it a credit card." or something

[4:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=270s) like that. So,

[4:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=272s) while that is possible,

[4:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=275s) um these agents,

[4:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=276s) uh because they consume so much data as

[4:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=278s) they go,

[4:39](https://www.youtube.com/watch?v=xKzU_3riL6s&t=279s) it's um

[4:41](https://www.youtube.com/watch?v=xKzU_3riL6s&t=281s) they pay in fractional amounts, so tiny

[4:44](https://www.youtube.com/watch?v=xKzU_3riL6s&t=284s) amounts, uh but at a very high

[4:46](https://www.youtube.com/watch?v=xKzU_3riL6s&t=286s) frequency.

[4:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=287s) Uh and credit cards and their fees are

[4:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=289s) just like not sustainable for this kind

[4:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=291s) of like economic model. Um you cannot

[4:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=293s) pay like 3% uh each time an agent tries

[4:56](https://www.youtube.com/watch?v=xKzU_3riL6s&t=296s) to make a one-cent transaction. And the

[4:59](https://www.youtube.com/watch?v=xKzU_3riL6s&t=299s) reason these transaction amounts are so

[5:01](https://www.youtube.com/watch?v=xKzU_3riL6s&t=301s) small is because on the sell side or on

[5:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=303s) the merchant side, they've realized that

[5:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=305s) these paywalls were actually catered for

[5:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=308s) humans, and now there's an entirely

[5:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=310s) different customer base which is trying

[5:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=312s) to like access their data, and they just

[5:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=314s) want like a subset of the data. So, you

[5:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=317s) could monetize that as a seller by just

[5:20](https://www.youtube.com/watch?v=xKzU_3riL6s&t=320s) offering that, by wrapping that in a

[5:22](https://www.youtube.com/watch?v=xKzU_3riL6s&t=322s) uh you know, in a paywall, and saying,

[5:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=324s) "Hey, I take one,

[5:26](https://www.youtube.com/watch?v=xKzU_3riL6s&t=326s) pay me 10 cents and grab this data."

[5:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=329s) And that's why these are

[5:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=331s) tiny um microtransactions, but highly

[5:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=335s) frequent. So, because the agents are

[5:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=336s) just like making these API calls

[5:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=338s) constantly.

[5:41](https://www.youtube.com/watch?v=xKzU_3riL6s&t=341s) So, what do these agents need? The

[5:44](https://www.youtube.com/watch?v=xKzU_3riL6s&t=344s) agents need um payments to work like the

[5:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=347s) internet.

[5:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=348s) So, they have to be real time,

[5:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=351s) low cost, programmable, and always on.

[5:57](https://www.youtube.com/watch?v=xKzU_3riL6s&t=357s) And that's why we've built the Circle

[5:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=358s) agent stack. So, it's the full stack

[6:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=360s) platform for the agent tech economy. And

[6:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=363s) what we mean by that, let's look at it

[6:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=365s) with a live demo.

[6:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=367s) Um yeah, wish me luck.

[6:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=372s) Okay.

[6:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=374s) So, I'll just explain

[6:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=376s) uh what I'm trying to

[6:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=379s) if I can get the

[6:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=383s) terminal. Okay.

[6:26](https://www.youtube.com/watch?v=xKzU_3riL6s&t=386s) Okay.

[6:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=389s) Let's

[6:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=391s) Mhm.

[6:34](https://www.youtube.com/watch?v=xKzU_3riL6s&t=394s) Pull it.

[6:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=396s) Yeah, I don't know.

[6:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=400s) Excuse me, can I

[6:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=402s) Yeah, I tried but

[6:46](https://www.youtube.com/watch?v=xKzU_3riL6s&t=406s) it's just not

[6:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=407s) I don't know where the placement of the

[6:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=408s) desktop is.

[6:52](https://www.youtube.com/watch?v=xKzU_3riL6s&t=412s) >> Can you escape out of this?

[6:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=413s) >> [snorts]

[7:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=420s) >> Okay.

[7:06](https://www.youtube.com/watch?v=xKzU_3riL6s&t=426s) Thank you. So, so what we have over here

[7:09](https://www.youtube.com/watch?v=xKzU_3riL6s&t=429s) are

[7:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=430s) two sessions. One is your regular cloud

[7:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=432s) code and on the other on the right hand

[7:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=434s) side is a cloud code that comes equipped

[7:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=437s) with Circle agent wallet. So, it has a

[7:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=439s) wallet which is funded and has the

[7:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=441s) ability to like make uh has the ability

[7:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=443s) to pay for premium content. And now uh

[7:26](https://www.youtube.com/watch?v=xKzU_3riL6s&t=446s) let me actually

[7:28](https://www.youtube.com/watch?v=xKzU_3riL6s&t=448s) just uh

[7:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=450s) quickly uh

[7:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=452s) add a task

[7:34](https://www.youtube.com/watch?v=xKzU_3riL6s&t=454s) to this.

[7:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=456s) Yep.

[7:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=458s) And run it.

[7:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=460s) So, I'll explain what I'm trying to do

[7:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=462s) over here, which is

[7:44](https://www.youtube.com/watch?v=xKzU_3riL6s&t=464s) Yeah, so So, the task I'm giving Claude

[7:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=468s) on and it's the same task on both the

[7:50](https://www.youtube.com/watch?v=xKzU_3riL6s&t=470s) terminals is

[7:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=471s) plan my trip for the FIFA World Cup

[7:54](https://www.youtube.com/watch?v=xKzU_3riL6s&t=474s) final.

[7:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=475s) So, just, you know, give me summary of

[7:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=478s) flights,

[8:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=480s) hotels, logistics. Also, like what are

[8:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=483s) the odds of like my favorite team

[8:04](https://www.youtube.com/watch?v=xKzU_3riL6s&t=484s) Argentina being in the final? Who is it

[8:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=487s) going to play? And stuff like that. Um

[8:09](https://www.youtube.com/watch?v=xKzU_3riL6s&t=489s) and also

[8:11](https://www.youtube.com/watch?v=xKzU_3riL6s&t=491s) what's the ticket prices in the

[8:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=492s) secondary market? How is the experience

[8:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=494s) of other people who've

[8:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=496s) actually been to the stadiums?

[8:18](https://www.youtube.com/watch?v=xKzU_3riL6s&t=498s) And

[8:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=499s) are there any FYIs and stuff like that?

[8:22](https://www.youtube.com/watch?v=xKzU_3riL6s&t=502s) Grab all of that.

[8:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=503s) Send me an email. And if possible uh

[8:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=507s) make me a make a phone call and tell

[8:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=509s) confirm that all of this has been

[8:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=511s) researched and you know, sort of brief

[8:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=513s) me on the summary.

[8:34](https://www.youtube.com/watch?v=xKzU_3riL6s&t=514s) So, we'll see like what's happening on

[8:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=516s) on both the terminals here.

[8:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=518s) And

[8:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=520s) Sorry, it's a bit hard to navigate. So,

[8:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=522s) as you can see, um

[8:44](https://www.youtube.com/watch?v=xKzU_3riL6s&t=524s) the left the vanilla Claude code has

[8:46](https://www.youtube.com/watch?v=xKzU_3riL6s&t=526s) spun out like a bunch of sub-agents. And

[8:50](https://www.youtube.com/watch?v=xKzU_3riL6s&t=530s) it's going about doing its research.

[8:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=533s) Similarly, on the right-hand side um

[8:56](https://www.youtube.com/watch?v=xKzU_3riL6s&t=536s) it's

[8:57](https://www.youtube.com/watch?v=xKzU_3riL6s&t=537s) actually like uh going through

[9:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=540s) the wallets and making like um

[9:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=543s) paying for all of these

[9:04](https://www.youtube.com/watch?v=xKzU_3riL6s&t=544s) uh premium content and we'll see like

[9:06](https://www.youtube.com/watch?v=xKzU_3riL6s&t=546s) what the results of it are.

[9:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=552s) So, as you can see, it's trying to make

[9:15](https://www.youtube.com/watch?v=xKzU_3riL6s&t=555s) a phone call to find sorry, an API call

[9:18](https://www.youtube.com/watch?v=xKzU_3riL6s&t=558s) to Stable and Rich. Um and it's paying

[9:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=561s) from its wallet.

[9:22](https://www.youtube.com/watch?v=xKzU_3riL6s&t=562s) It's set up a guardrail of like, "Hey,

[9:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=564s) max amount is 15 cents." The beauty of

[9:28](https://www.youtube.com/watch?v=xKzU_3riL6s&t=568s) uh

[9:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=569s) having an agent with a wallet is

[9:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=572s) you

[9:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=573s) sort of build these guardrails into the

[9:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=576s) wallet. And you don't have to as a human

[9:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=578s) approve every single transaction

[9:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=580s) because that would just not scale

[9:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=582s) because these agents are just making

[9:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=583s) these ones and five cents, 10 cents

[9:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=585s) transactions. You want to like enforce

[9:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=587s) those guardrails which is hey, this is

[9:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=589s) the max amount you can send spend per

[9:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=591s) session or this is the max cap you can

[9:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=593s) do per day and stuff like that. So,

[9:56](https://www.youtube.com/watch?v=xKzU_3riL6s&t=596s) the agent is still spending within the

[9:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=598s) guardrails that you set but it is

[10:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=600s) autonomous enough to like make these

[10:02](https://www.youtube.com/watch?v=xKzU_3riL6s&t=602s) individual API calls.

[10:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=607s) So, let me just

[10:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=610s) look at what

[10:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=613s) the vanilla one is

[10:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=616s) looking up and doing some research for

[10:18](https://www.youtube.com/watch?v=xKzU_3riL6s&t=618s) hotels.

[10:22](https://www.youtube.com/watch?v=xKzU_3riL6s&t=622s) Yeah, um

[10:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=625s) flights are coming in.

[10:28](https://www.youtube.com/watch?v=xKzU_3riL6s&t=628s) Also like in the prompt like try to like

[10:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=630s) tell the agent to

[10:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=632s) wrap this whole thing up within 6 to 8

[10:34](https://www.youtube.com/watch?v=xKzU_3riL6s&t=634s) minutes in the interest of time. So,

[10:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=635s) let's see if we're able to like get an

[10:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=638s) email and a phone call done

[10:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=640s) in the same time.

[10:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=651s) Let me also walk you through

[10:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=655s) what the agent's doing if I can grab.

[11:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=665s) Yep, as you can see over here the agent

[11:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=668s) was able to like make an API call to

[11:11](https://www.youtube.com/watch?v=xKzU_3riL6s&t=671s) the poly market data

[11:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=673s) via a provider called Block Run and

[11:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=677s) it provided a query

[11:20](https://www.youtube.com/watch?v=xKzU_3riL6s&t=680s) and again

[11:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=681s) set the max amount guardrails

[11:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=685s) and is now passing all the results.

[11:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=713s) >> All right.

[11:54](https://www.youtube.com/watch?v=xKzU_3riL6s&t=714s) So,

[11:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=715s) let's go back to the

[11:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=718s) main subject main agent here.

[12:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=743s) Yep.

[12:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=743s) And this is where I think you'll see on

[12:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=745s) the left-hand side that the agent gets

[12:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=747s) stuck because

[12:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=749s) the agent just does not have the ability

[12:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=751s) uh it cannot send out an email natively.

[12:34](https://www.youtube.com/watch?v=xKzU_3riL6s&t=754s) So, what it's doing is it's using my uh

[12:37](https://www.youtube.com/watch?v=xKzU_3riL6s&t=757s) it's just like adding a draft into my

[12:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=760s) Gmail account uh that is logged in, but

[12:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=762s) it just cannot send it to someone. Uh

[12:44](https://www.youtube.com/watch?v=xKzU_3riL6s&t=764s) whereas the other agent on the

[12:46](https://www.youtube.com/watch?v=xKzU_3riL6s&t=766s) right-hand side will just be able to use

[12:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=769s) um a provider, pay it, and send an

[12:52](https://www.youtube.com/watch?v=xKzU_3riL6s&t=772s) email.

[13:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=780s) Now, let's see like

[13:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=783s) this one's uh the

[13:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=785s) the other agent is also like

[13:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=787s) uh is about to like send an email and

[13:09](https://www.youtube.com/watch?v=xKzU_3riL6s&t=789s) place the call, so let's see.

[13:11](https://www.youtube.com/watch?v=xKzU_3riL6s&t=791s) Does.

[13:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=810s) >> Okay.

[13:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=812s) So,

[13:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=813s) as the

[13:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=815s) I think the left agent, the vanilla

[13:37](https://www.youtube.com/watch?v=xKzU_3riL6s&t=817s) cloud goods finished, and as you can

[13:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=818s) see,

[13:39](https://www.youtube.com/watch?v=xKzU_3riL6s&t=819s) it's sort of like made a confession that

[13:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=822s) yeah, it cannot have It does not have

[13:44](https://www.youtube.com/watch?v=xKzU_3riL6s&t=824s) the ability to make a phone call. So,

[13:46](https://www.youtube.com/watch?v=xKzU_3riL6s&t=826s) it's just like providing me the

[13:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=828s) highlights over here in the terminal

[13:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=829s) itself. Um and

[13:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=833s) now, uh whereas on the right-hand side,

[13:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=835s) the email's been sent. Now, let me try

[13:59](https://www.youtube.com/watch?v=xKzU_3riL6s&t=839s) to

[14:02](https://www.youtube.com/watch?v=xKzU_3riL6s&t=842s) actually show you the email that we got,

[14:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=845s) I wish.

[14:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=850s) Grab this somehow.

[14:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=859s) Okay, I'm going to make

[14:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=861s) make the phone call.

[14:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=865s) Okay.

[14:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=875s) Just going to grab my

[14:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=880s) thing here, and then

[14:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=883s) let's look at the email.

[14:46](https://www.youtube.com/watch?v=xKzU_3riL6s&t=886s) So,

[14:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=891s) yep, there we go.

[14:52](https://www.youtube.com/watch?v=xKzU_3riL6s&t=892s) So, I got this email. Oh, this is the

[14:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=895s) old one. Let's see the new one.

[14:59](https://www.youtube.com/watch?v=xKzU_3riL6s&t=899s) Yep.

[15:01](https://www.youtube.com/watch?v=xKzU_3riL6s&t=901s) This is the one that we just received

[15:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=903s) like 2 minutes ago.

[15:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=905s) And

[15:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=907s) yeah, it has all the

[15:09](https://www.youtube.com/watch?v=xKzU_3riL6s&t=909s) details that it was able to like find,

[15:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=912s) including like getting to the stadium,

[15:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=914s) open stadium and maps. It was able to

[15:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=916s) like,

[15:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=917s) you know, find all of these.

[15:20](https://www.youtube.com/watch?v=xKzU_3riL6s&t=920s) And then,

[15:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=923s) what to expect by looking at like Reddit

[15:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=927s) tickets, etc.

[15:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=930s) So, I'll wait for the call but in the

[15:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=932s) interest of time it takes sometimes

[15:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=935s) a few minutes for the call to come in

[15:37](https://www.youtube.com/watch?v=xKzU_3riL6s&t=937s) but

[15:39](https://www.youtube.com/watch?v=xKzU_3riL6s&t=939s) let's see and I'll move on. So, how does

[15:42](https://www.youtube.com/watch?v=xKzU_3riL6s&t=942s) this work uh

[15:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=943s) in the background?

[15:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=945s) Is

[15:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=948s) Yeah, let's get back to this. Let's

[15:57](https://www.youtube.com/watch?v=xKzU_3riL6s&t=957s) Yeah, so so as you can see like the

[15:59](https://www.youtube.com/watch?v=xKzU_3riL6s&t=959s) agent on the right hand side with the

[16:01](https://www.youtube.com/watch?v=xKzU_3riL6s&t=961s) wallet was able to just make a bunch of

[16:04](https://www.youtube.com/watch?v=xKzU_3riL6s&t=964s) these API calls and pay for it. While

[16:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=967s) blockchains make all of these things

[16:09](https://www.youtube.com/watch?v=xKzU_3riL6s&t=969s) theoretically possible, there are there

[16:11](https://www.youtube.com/watch?v=xKzU_3riL6s&t=971s) are also some bottlenecks because uh

[16:14](https://www.youtube.com/watch?v=xKzU_3riL6s&t=974s) even the most efficient blockchains

[16:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=976s) have a gas fee and these small

[16:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=979s) transactions just don't scale because

[16:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=981s) the gas fee will again be a significant

[16:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=984s) sort of

[16:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=985s) fraction of the actual transaction. But

[16:28](https://www.youtube.com/watch?v=xKzU_3riL6s&t=988s) it is important to have gas fees because

[16:30](https://www.youtube.com/watch?v=xKzU_3riL6s&t=990s) they prevent the network from spam and

[16:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=992s) abuse.

[16:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=993s) Um and blockchains also have some

[16:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=995s) throughput limitations because there are

[16:37](https://www.youtube.com/watch?v=xKzU_3riL6s&t=997s) other use cases that run on blockchains

[16:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1000s) and block space is shared

[16:41](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1001s) infrastructure. So, the problem for

[16:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1003s) agents is unpredictable latency and

[16:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1005s) degraded performance under load.

[16:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1007s) So, what we did for that

[16:50](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1010s) is

[16:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1011s) essentially uh we built a new um

[16:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1015s) infrastructure layer on top of our intra

[16:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1018s) product called gateway. So, it's called

[17:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1020s) nano payments. It's built for sub cent

[17:02](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1022s) transaction sizes for as low as one

[17:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1023s) micro cent.

[17:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1025s) Uh it supports

[17:06](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1026s) um it is gas free for the seller and

[17:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1028s) it's instantly cross-chain.

[17:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1032s) And

[17:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1033s) the way it works is you essentially you

[17:16](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1036s) just fund um

[17:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1037s) your wallet and then Oh, sorry. While I

[17:20](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1040s) explain this, let's listen to the actual

[17:22](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1042s) call that came in.

[17:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1043s) And

[17:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1044s) >> Hi Harsha, here is your World Cup final

[17:26](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1046s) trip

[17:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1047s) >> I don't know if it's part of it.

[17:28](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1048s) >> at MetLife Stadium. Fly SFO to either

[17:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1051s) EWR or JFK non-stop. SFO is showing live

[17:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1055s) arrival delays today, so build buffer.

[17:37](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1057s) >> Awesome.

[17:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1058s) Can you tell me how do I get to the

[17:41](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1061s) stadium from my hotel?

[17:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1065s) >> On match day, take NJ Transit to

[17:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1067s) Secaucus Junction, then the Meadowlands

[17:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1069s) Rail Spur direct to the stadium. Budget

[17:51](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1071s) about an hour before receipt.

[17:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1073s) >> Thank you. I'll read the rest of it in

[17:55](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1075s) my email. Thank you.

[18:01](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1081s) >> You're welcome. Have

[18:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1083s) >> All right. So, that was just a quick

[18:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1085s) demo of like how you can have like AI

[18:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1088s) agents.

[18:09](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1089s) Um if they're equipped with a wallet,

[18:10](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1090s) they can do a lot of things

[18:12](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1092s) with the

[18:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1093s) as opposed to an agent that does not

[18:15](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1095s) have a wallet. So,

[18:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1097s) I have a couple of more minutes, so I'll

[18:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1099s) just walk you through how this

[18:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1101s) technology works underneath.

[18:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1103s) So,

[18:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1104s) if you have a wallet and you funded it

[18:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1107s) with USDC, it's very easy because Circle

[18:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1109s) works with a bunch of providers to

[18:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1111s) on-ramp your actual US dollars into

[18:33](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1113s) USDC. And from there, you can deposit

[18:36](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1116s) the funds into a smart contract. The

[18:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1118s) next thing it does is

[18:41](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1121s) the agent just has to like sign these

[18:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1123s) off-chain authorizations,

[18:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1125s) which are essentially cryptographic

[18:47](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1127s) signatures saying, "I

[18:49](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1129s) am paying this address this particular

[18:52](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1132s) amount of money."

[18:53](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1133s) And then

[18:54](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1134s) the server just has to like relay this

[18:56](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1136s) to Circle and within a few hundred

[18:58](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1138s) milliseconds,

[19:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1140s) this the server knows

[19:02](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1142s) the merchant knows that, you know, the

[19:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1145s) user has the funds and is able to

[19:07](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1147s) release the actual resource that the

[19:09](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1149s) agent requested. And with this, you

[19:11](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1151s) avoid the

[19:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1153s) issue of like you know latencies and

[19:15](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1155s) stuff that are associated with actually

[19:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1157s) settling every single transaction on

[19:19](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1159s) chain and this

[19:21](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1161s) the agents are able to like pay for

[19:23](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1163s) things

[19:25](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1165s) at the speed at which they operate. So

[19:27](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1167s) in conclusion the the the way the stack

[19:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1169s) would work is you have Circle agent

[19:32](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1172s) wallets which give you the ability to

[19:35](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1175s) equip your agents with wallets.

[19:38](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1178s) The agents have can now hold their

[19:40](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1180s) money, spend that money autonomously but

[19:43](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1183s) within the guardrails that you set. The

[19:45](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1185s) wallets enforce those guardrails and

[19:48](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1188s) then on the sell side the merchants are

[19:50](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1190s) able to like just

[19:52](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1192s) wrap their endpoints and resources and

[19:54](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1194s) monetize it with a few lines of code

[19:57](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1197s) using our SDKs.

[19:59](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1199s) Then

[20:00](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1200s) USDC and nano payments is the layer

[20:03](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1203s) underneath it which sort of helps settle

[20:05](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1205s) these transactions at the speed at which

[20:08](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1208s) agents operate which is sub second. So

[20:11](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1211s) and that this is how it scales

[20:13](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1213s) and you can give it a try yourself by

[20:17](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1217s) going to agents.circle.com.

[20:20](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1220s) It's just a couple of clicks and

[20:24](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1224s) you will have your agent equipped with a

[20:26](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1226s) wallet and ready to like you know make

[20:29](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1229s) these phone calls and things like that.

[20:31](https://www.youtube.com/watch?v=xKzU_3riL6s&t=1231s) So yeah, thank you.
