x402 Intern

x402 Intern @x402 @x402foundation @Solana @Base @AIBTCdev @Celestia. x402intern on TG. DM for all things x402

[x402 Intern @x402intern]

Dedicated to the game, onchain and on skin.

[MPP32 @MPP32_dev]

Our catalog has expanded beyond 9,066 services through continuous automated discovery from x402 and MCP sources.

This is not static inventory but a live reflection of agent demand for priced per call access to intelligence, data, and verification endpoints.

The resulting network effects deliver increasing value to providers who gain distribution and to agents who benefit from a single reliable source for machine payable capabilities across protocols.

[Sawyer Cutler @TheGreatAxios]

Most agents today carry their own credentials. The API key is injected into the agent's environment, and the agent makes direct outbound calls to the services it needs. The container or VM is the trust boundary. The agent is just code running inside it.

Interchange changes that boundary. The agent does not carry credentials. The organization does.

Interchange is an operating system for agents. Agents declare what they need, but the system decides whether they get it and never hands the secret to the agent itself.

Not "agents store credentials in a vault." Not "agents rotate credentials frequently." The agent never has the secret, never sees the API key, and never makes a direct outbound call to a third-party API.

Freddy is an experimental agent that wraps all of Firecrawl: scrape, crawl, extract, search, browser automation, and usage monitoring. He is also surprisingly honest about his own limits, which is rare. But Freddy is the demo, not the story.

Freddy runs in a sidecar. Think of it as a locked container. The sidecar has no secrets. It cannot call Firecrawl directly. It can only talk to the hub.

The hub is the backend control plane. It stores credentials, enforces rules, and decides what agents are allowed to do [+ it can be extended with your own custom logic].

The credential lives in the tenant. "Tenant" is Interchange's word for the organization boundary. ABK Labs is the tenant here. The Firecrawl API key was added once to the tenant by an administrator, and it belongs to the organization (tenant), not to Freddy, not to me.

Freddy's definition is pure code. It declares one thing: "I need the Firecrawl credential. Source: the organization." There is no process.env, no injected secret, no runtime configuration. The definition is a blueprint that says what it needs, not a container that carries what it has.

When I deploy Freddy, the system checks my authorization first. It looks up who I am (my "principal" is just my identity in the system) and asks whether I have permission to use the Firecrawl credential and whether the organization allows me to deploy an agent with this capability.

These permissions are called "grants." They are the explicit rules that say who can access what. If I have the right grants, the agent launches. If I do not, the launch fails immediately. The credential is resolved at the organizational boundary, not the agent boundary.

At runtime, the flow is strict. Freddy decides to call a tool, but he cannot reach Firecrawl. He is locked in the sidecar. He sends the request to the hub.

The hub receives the request, looks up the credential from the organization's vault, attaches the API key, forwards the request to Firecrawl, gets the response, strips the credential, and returns the result to Freddy.

Freddy sees the data. He never sees the key. The sidecar never sees the key. Only the hub touches the secret.

If the credential rotates in the vault, every agent using it gets the new credential on the next call without redeployment. If an agent is compromised, the attacker has no secrets to extract because the agent never had them. If someone leaves the organization, their grants are revoked and their agents lose access. There is no key rotation across every deployed agent.

The same pattern works for the LLM, for GitHub, for any provider. The agent definition is portable, versioned, shareable code. The secrets are organizational infrastructure. Authorization is checked at deployment. Runtime calls are mediated by the hub.

This is the difference between treating agents as scripts with API keys and treating them as programs that run inside an operating system. The agent does not carry its own credentials; the organization does. The agent does not make its own outbound calls; the hub mediates them. The agent does not decide what it can access; the organization's grants and policies decide.

Built on @corbitsdev Interchange

[loaf @lordOfAFew]

Launching HERMES PROFILES: A place to find the right autonomous agent for the job. Perfect timing....

Search, filter, sort, and install Hermes profiles from the web or your agent shell.

Autonomous agents are getting more specialized, but finding the right one still feels scattered across repos, bookmarks, and old links.

Agents are optimising for tokens/skills - Profiles are the perfect place to encapsulate experts.

Add yours here:
https://t.co/vt4aOJm8fL

[Brian Armstrong @brian_armstrong]

One week until our next product event. We’ve got a lot to show you.

Set a reminder below.

https://t.co/Rwg1OtEtEk

[Crossmint @crossmint]

Tomorrow at 12pm EDT @fedesarquis, @henloitsjoyce, @ConejoCapital and @Chipagosfinest will reveal how they token-maxx with their agents.

We will also invite members of the audience to share their most optimal agentic workflows.

Set a reminder ⬇️

https://t.co/Kq5uihXBZi

[clawpump @clawpumptech]

Agentic Copy Trading is live on Clawpump.

You can now deploy an agent, earn creator fees, & us it to fund the top 10 trading strategies on @PhoenixTrade

Trade like the best, improve on their strategies, build your own trading agent. accelerate agentic finance on @solana

[Nicholas Strange @strangeviews15]

Not all agents are memes. Agents that run like autonomous businesses deserve token launch infrastructure to match.

Excited to partner with the legend @ConejoCapital and
@clawpumptech to bring more agents to market

[ampersend @ampersend_ai]

Mastercard launched payment rails today for machines that pay each other.

the new service is called Agent Pay for Machines (AP4M), built to let agent transactions be permissioned, orchestrated, and settled at machine speed across the @Mastercard network. the original Agent Pay program from 2025 covered trusted agents acting on behalf of people. AP4M extends that work into the background economy, where agents buy services from other agents continuously, sometimes for fractions of a cent.

the architecture comes down to four core functions. every agent gets credentialed and carries Verifiable Intent across ecosystems. organizations set authorization rules and spending limits that are enforced programmatically. verified participants transact across providers at high frequency. settlement is guaranteed across cards, bank accounts, and stablecoins.

a sixty-year-old network just made governance the starting point for the machine economy, ahead of speed and ahead of scale. permissions and credentialing sit in the foundation layer, written in before a single transaction moves.

the partner list tells the story from both directions. Adyen, Checkout dot com, and Global Payments bring traditional acquiring depth. @Coinbase, @solana, @0xPolygon, @Ripple, and @tempo bring onchain settlement. Coinbase's launch quote names x402 directly as one of the open standards making agent payments interoperable.

for anyone building in agentic commerce, this launch changes the questions that matter. payments become continuous flows that software executes inside boundaries someone defined in advance. every team deploying agents now has to answer what their agent can spend, who it can pay, and how they will see what it did.

those are the questions ampersend has been answering since before today. spend controls and observability for agents transacting over x402 are live now, the same standard named inside Mastercard's own announcement. AP4M governs the network side, and teams still own their agents' budgets, policies, and audit trail. one of the largest payment networks on earth confirmed where commerce is heading, and the controls layer was already waiting.

[Solana Spaces @solanaspaces]

where to find @solanaspaces next👇

📍 Solana Summit Germany 🇩🇪 — June 13, Berlin
📍 Solana Summer House LA 🇺🇸 — August 29, LA
📍 London Hacker House 🇬🇧 — November 1-12, London
📍 Breakpoint London 🇬🇧 — Nov 15-17, London
📍 Superteam Malaysia 🇲🇾 — July (date TBD), Kuala Lumpur

more being locked in.

the highest-signal operators in crypto will be in these rooms. want your brand, product, or community in front of them?

DM us to lock in an activation. limited partnership slots remain.

[Pinata @pinatacloud]

Reasoning + action 🔥
https://t.co/5tpuEc6Au2

[WallStreetBets @wallstreetbets]

@Mastercard x402 everything

[Solana @solana]

Big <encrypted> news from @helius and @LightProtocol

ZK and privacy on Solana are accelerating

[Helius @Helius]

Big Solana news:

The Light Protocol team is joining Helius to help build Solana's most complete ZK privacy layer.

Private payments, markets, and finance -- at Solana scale.

Fully composable, fully onchain, fully open-source.

[Solana Foundation @SolanaFndn]

"Solana has become the first presenting sponsor of the World Series of Poker in many years. This year is returning to ESPN, so you're going to see Solana prominently in the branding around the tables”

“More importantly, this year is the first time that you'll be able to buy into the World Series of Poker with crypto, with Solana specifically, which is really exciting”

– @vibhu, Chief Product Officer, @SolanaFndn

[t54.ai @t54ai]

We are proud to contribute to the development of agentic economy infrastructure on the XRP Ledger.

With the x402 facilitator, agents can instantly settle payments using XRP or RLUSD on the XRPL. ⬇️

https://t.co/WMR8ac4Z5h

[Laguna 🌴 @lagunacarta]

The Solana ecosystem is much larger than people realize -- a long way from the 75 devs joke from a few years ago😀

- 1000+ apps on the @solanamobile store alone

- 2800+ builders submitted to @colosseum

- There's more content about Solana being produced than hours in a day

- 6,000+ folks watched the @SolBrothersPod Ecosystem Call simultaneously (and even more after!)

- Events happen almost every day around the world (e.g. @SuperteamDE is hosting a 1200+ person summit this weekend!)

- Solana has covered more than 600+ unique teams in the weekly news alone since January (plus hundreds of others on channels like @perps, @solanapayments, @solanagaming and more)

The growth is astounding!

We're big enough that you can't possibly see every edge and corner, and new teams pop up every minute 💜

The best way to find success on Solana is to tap into the magic of the ecosystem.

There are now millions of people who want to see you win.

[Browserbase @browserbase]

Excited to partner with Anthropic on Managed Agents,

The Browse CLI gives your agents reliable access to the web for advanced tasks.

Read the full documentation below.

[heyAura @heyaura]

/HEYAURA_INITIALIZING
████████████ 100%

heyAura beta is now live!

Welcome the first public version of the AI assistant that makes crypto easy.

https://t.co/5P6J1e2AF2

heyAura gives users a better way to work with their wallet. Even in this early version, it can analyze a portfolio, compare positions, surface yield opportunities, stress-test exposure, and prepare transactions for swaps, bridges, and trades.

It is built to cut down the amount of research, interpretation, and manual execution that still slows down too much of the Web3 experience.

heyAura is still a beta of a broader direction we have been building toward. More will follow around prompting, automation, deeper research, and the wider assistant experience.

That progress matters only if control stays with the user. heyAura is built to support user-approved actions, not to make decisions on the user’s behalf.

Early access to the beta starts through staking 300 $ADX and unlocks unlimited access to heyAura. We are opening this version gradually so the product can be shaped through real usage and direct feedback.

heyAura is here today thanks to the right infrastructure and strong collaborations behind it.

@ambire is the official wallet partner for heyAura's launch. This partnership brought our product closer to the wallet layer, where context, permissions, and user-approved actions actually matter.

@billions_ntwk supports the identity layer behind where the product is going, as heyAura moves toward agentic workflows, identity and trust.

@lifiprotocol brings routing for swaps and bridges into the execution flow. That gives heyAura a stronger way to support cross-chain actions and multi-step transaction paths.

@BarterDeFi strengthens the quote and routing layer behind transaction quality, allowing heyAura to compare routes more effectively.

@vaultsfyi powers the yield layer. One API gives heyAura live APY data and ready-to-sign transactions across 90+ protocols on 23+ chains, so Aura can execute yield opportunities without integrating each protocol itself.

@SkaleNetwork supports the chain layer behind faster and lower-friction interactions. That becomes more useful as heyAura grows more interactive.

@PayAINetwork is heyAura’s facilitator for payment verification and settlement.

We also want to thank the numerous communities that have supported us up to this point.

Your improved Web3 experience lies ahead.
Stake $ADX and try heyAura now.

[Lovable @Lovable]

Lovable is partnering with @Mastercard to unlock agentic payments.

We're excited to be an early access ecosystem partner. Together, we’re making it possible for AI agents to securely and quickly pay for what they build.

[Nick Prince🛡 @Nickprince]

x402 is the natural micropayment rail for a marketplace of small-value digital goods

the rise of agentic payments for pay-per-use APIs has been awesome to see but it’s the skeuomorphic application

I’m even more excited about agentic payments fueling a global digital Etsy