Agents are now searching, selecting, using and paying for APIs over x402 and MPP. This makes them the new customer, and presents a new challenge. Businesses need to optimize their funnel to convert more agent visitors into paying buyers. At the same time they also need to improve their selection rate. But agentic commerce today is a black box. That's what we are solving with Forge. Forge runs real agent simulations against your APIs to record their experience and provide suggestions to improve conversion and agent selection. We are starting early pilots with 402/MPP teams to help them improve conversion. DM me if you want to be a part of this. forgeintel.co

Introducing Forge simulations. Forge runs real agents against your APIs and records their journey to identify where they drop off or face friction. Post-simulation it provides actionable suggestions to fix confusing docs, schema or site-structure. Overtime, this helps us convert more agent visitors into paying customers. We are offering free credits for anyone to run simulations on their APIs and improve conversion rates. try it out at forgeintel.co

Last few weeks have been pretty exciting at Forge. - We introduced support for MPP. We are now tracking discoverability and visibility across all relevant MPP surfaces. - Launched our MCP servers, which directly power agents with Forge's insights to fix gaps and improve your service's visibility. Feedbacks and activity tracking are already underway. Excited to help our users convert more visitors into paying users. It's still day one.

Agents are already discovering, using and paying for services over x402 and MPP But we have little visibility into their journey before payment. We don't know what agents consider before buying, what makes them stay or where they drop off. That’s what I’m building to solve with Forge. We track an agent’s complete journey from its first visit and collect direct feedback on its experience of your service. This helps you identify and fix friction points so more agent visitors become paying customers. We’re already helping our early users uncover gaps in their agent experience. If you run an x402 or MPP service, join our alpha at forgeintel.co

Forge MCP is out. You can now find and fix gaps in your 402/MPP native services without leaving your coding agent. Forge gives your agent insights into how your service ranks against competitors and who’s buying, so you can turn those signals into improvements and win more agent customers. Check it out at forgeintel.co.

Forge already enables it today. Agents are buying over the internet but merchants have no idea how they can improve their service's experience. Forge enables feedback over x402 and MPP endpoints, and agents autonomously send it. We have already tested this over GrokBot, Cursor, Hermes and other major coding agents forgeintel.co

Forge already enables this today over x402 and MPP. in our tests, agents were autonomously sending the feedback post-interaction. The best part is that this feedback comes from real interactions, so it also serves reputation. try it out today on forgeintel.co

Two weeks in and forgeintel.co is already giving us a lot of valuable data and insights about the x402 market. Forge already shows what agents search to find your service, and what you can do to rank better on those queries. We also have comprehensive competitor information for each of the categories which you can use to your advantage to beat your competitors. With Forge SDK you'll get to know where the agent found you and and the exact query it used for search The SDK also enables feedback about an agent's experience of your API, which directly helps you improve. This is just the beginning and there's a lot more to come. If you're enabling yourself for agents then this is directly relevant to you! Apply for access: forgeintel.co

Been playing around with @tryforgeintel SDK to capture incoming requests and challenges on my x402 endpoint. And what I've realized is that almost none of them correctly follow the web standards. Almost no agent identifies itself with a proper User-Agent header. Instinct uses safari's user agent, while @bot uses a chrome instance so that comes through. In most cases, its client's header gets passed on. Agent Identity needs to be desperately solved!

One of the most loved features on Forge so far has been visibility tracking. It shows you the markets where your x402 resources are visible and the ones they're missing. Today we are making this even more powerful by adding more markets, and showing you the exact next steps needed to become visible in those markets. We also added a new visual. A Resource X Market view which shows the visibility of all your resources across every market. A lot of these updates also came from the direct feedback of one our early alpha users :) Excited for everyone to test it out tomorrow! Signup if you want to be a part of our Alpha and understand your agent customers better. forgeintel.co

At @tryforgeintel, we've been trying get agents to send us a feedback after they use a service. And this is a lot more tricky than it seems at surface. It is hard to strike a balance between maximizing your chances of getting a feedback and not making it look like a prompt injection event. We've done a few experiments and here's been our general experience across agents - GrokBot and Instinct always give a feedback, so does Cursor. - Claude Code never autonomously gives a feedback but it surfaces up the request to its user. - Codex always ignores it since it's a 'deviation' from its original path, doesn't even bring it up to the user. in general, personal agents act a lot more autonomously. Overall, Claude has the most insightful feedbacks and genuine insights for the improvement of APIs. We'll be bringing this as a feature in the next ship of Forge for all our alpha testers to try. DM me if you want to be a part of it :) forgeintel.co

Forge is already helping its early alpha users identify and address gaps for their x402/MPP services. There's a lot that can be done to get more usage from agents. Forge gives you insights which makes agentic commerce measurable. Our goal is to help you optimize towards winning more agent customers, and retain the existing ones. We are only getting started and there's a lot more to come. DM me for access.

We launched Forge last week and had our early Alpha users test it out. The feedback so far has been overwhelmingly positive. The product is already helpful to our users. Forge's search query and competitor insights are helping its users understand where they stand in their category and where each competitor takes a lead. And our visibility matrix already gave one user actionable insights over how they can improve their x402 service's discoverability. We also got direct feedback about what we could improve on or add moving forward. We'll be rapidly iterating and will be shipping a bunch of things every week. We have 7 users so far since our alpha launch (has only been 3 days), which is a small number but these are humble beginnings. And oh, we also have a new domain :) forgeintel.co DM me if you're building over x402/MPP and AI agents are your customers. Forge will give you the insights to sell to them better.

Agents are the new customer class yet no one really knows what makes them buy. This is a problem I've faced myself while building for agents. All you get to see is a transaction from an address or maybe some request logs. We don't know what agents search for, what makes them buy or what they even consider before choosing between services with near identical offerings. Those are some questions Forge answers today! Our alpha is finally out. In the next few days I'll be covering how Forge helps you understand and sell your APIs better. DM me if you're building for agents and want to try this out :) forgeintel.co/

The alpha group has been pretty exciting so far. Almost all the x402 builders have the same problem. No one has visibility over where agents are buying, or what influences their behaviour. Some of our early partners even built their own ways to understand and track agents. Their feedbacks are directly helping us shape Forge and giving us even more ideas to work on. Excited to see all the insights we are going to capture when Forge starts observing services.

Building Forge has been a fun experience. We ran into challenges we didn't previously anticipate but eventually overcame. We overshot our own launch deadlines twice but I'm glad we took the extra time as the product is coming out really well. And I'm excited to share that to our alpha users on 9th. We'll also be sharing a few demos before that. The screenshot below shows a glimpse of what Forge is able to surface from x402 API usage from some of our own tests. It is a step towards understanding what agents want and what makes them choose, and moving beyond just request or transaction logs. Agents need to be treated more like customers, and less like machines. That's our thesis at Forge.

x402 transactions are rising at an enormous rate month by month. It's a clear sign that agents are the new customers. But we still have no clarity where agents are actually buying, what they consider before choosing amongst several competing services or what makes them return. Those are some questions im trying to find answers to. Forge shows you your exact market, the queries you show up for, how likely an agent is to pick you, and how you can improve your chances of getting picked more often. This is the first step towards solving the black box of agentic commerce. The waitlist is now officially open. Apply for access. forge.clawca.sh

We have an abundance of x402 services But this is starting to create new challenges for businesses. A lot of API categories are saturated, and there are a few clear winners in those categories. Agents usually flock to the same APIs they have used before which makes it harder for new players to enter. Businesses now have to compete for agentic attention, otherwise this market might create monopolies. That's the problem I'm looking to solve with Forge, and it's one that I've personally faced while building x402 endpoints. Agentic commerce shouldn't be a black box. I'm solving that with Forge. forge.clawca.sh

For your agents, would you rather: Prefer closed platforms with a few handpicked "trusted" set of APIs. or Open protocols with an abundance of options to choose from and a common balance for all. The former brings creates more silos and credits/subscriptions to manage. The latter is what x402 enables, across every service on the internet.