x402 Ventures (@402BoxIO) header
x402 Ventures (@402BoxIO) profile picture

A builder collective experimenting with agentic toolkits and products. Building around the x402 protocol. Plugins live for @opencode, @claudeai, and @openclaw.

Joined December 2025
Photo by x402 Ventures (@402BoxIO)Photo by x402 Ventures (@402BoxIO)Photo by x402 Ventures (@402BoxIO)Photo by x402 Ventures (@402BoxIO)Photo by x402 Ventures (@402BoxIO)Photo by x402 Ventures (@402BoxIO)Photo by x402 Ventures (@402BoxIO)Photo by x402 Ventures (@402BoxIO)
x402 Ventures retweeted
I built something I've been wanting to exist for a while. It's called Laterr. You write a message to your future self, pick a date, and it gets delivered to you by phone call or email. It's live: laterr.app
1
1
1
7
901
x402 Ventures retweeted
A little sneak peek at how we use OpenClaw CRM. (@402BoxIO) It's not about basic automations, it's about workflows that are actually valuable. Train your OpenClaw bot, instead of "add a lead", let it run a web search, pull context, then create the lead.
2
8
552
x402 Ventures retweeted
Our x402 skills are now available on @openclaw. We’re excited to share that 3 of our x402 skills are now available on @openclaw for everyone to download. You can get them by sharing the links belwo with moltbot or by downloading from Clawdhub. What skills are available? → X Search (x402) clawdhub.com/TzannetosGianni… AI powered X/Twitter search for real time trends, breaking news, sentiment analysis, and social media insights. Use it when you want to search Twitter/X for topics, hashtags, viral content, or public opinion. Costs: $0.05 USDC per request via the x402 protocol on Base. → Find People (x402) clawdhub.com/TzannetosGianni… Open source intelligence (OSINT) tool for researching individuals, including professional backgrounds, career timelines, due diligence, competitive intelligence, and investor research. Use it when you need to research people, verify credentials, or gather professional information. Costs: $0.15 USDC per request via the x402 protocol on Base. → Alpha Finder (x402) clawdhub.com/TzannetosGianni… Market oracle for mainly PM market intelligence, including Polymarket and Kalshi research, probability assessments, market sentiment analysi. Use it when you want to research prediction markets, analyze betting odds, or spot market inefficiencies. Costs: $0.03 USDC per request via the x402 protocol on Base.
4
3
1
12
638
x402 Ventures retweeted
An experiment on benchmarking and evaluating LLM outputs x402 is the core of our experimenting around a lot of things like PolyAI, our plugins and more. However, we spent the past week focusing on a different question: How do you actually evaluate an LLM’s output? In most teams, the workflow looks like this: Create a prompt → run it on different LLMs → get an output → manually judge it → tweak the prompt → repeat. This works, until you try to scale it. A few problems show up quickly. 1/ Is the final output the only thing worth evaluating? In agentic workflows, failures usually happen earlier, in reasoning, tool usage, state handling, or execution flow. This gets even harder when agents need to run in isolated environments, like in cases such as PolyAI, where shared state or leaked context can invalidate results. 2/ How do you evaluate consistency across models? If something breaks on Sonnet 4.5, it doesn’t mean it broke the same way on GPT-5.2. Manually inspecting outputs across models doesn’t scale and hides where things actually fail. 3/ When something works, do you know why? Was it the prompt, the agent path, or luck? Can you reproduce it reliably? So we tried a different approach. We added tracing and basic evaluation into the workflow. The goal wasn’t to remove humans from the loop, but to move human judgment to a level where it can scale. Instead of judging only the final output, we observed full runs, reasoning steps, tool calls, failures, and execution paths, across isolated environments, using monitoring and tracing via @langfuse, alongside our @opencode instances. Patterns started to appear. → Agents generated content but never saved it. → They referenced tools that didn’t exist. → They returned plans instead of results. → Sometimes they stopped entirely. The surprising part wasn’t the failures, but how repeatable they were. With proper isolation and monitoring, we can now compare models running the same tasks and see where cheaper models behave almost identically to expensive ones. In practice, testing multiple models and combinations can reduce costs by 10x to 100x for specific tasks. Some findings: > Open-source models can outperform paid ones for narrow skills > Agents doing the same job fail in different, repeatable ways > Prompting gets better, instead of guessing, you can see where it breaks At this point, it’s less about picking “the best model” and more about understanding where each model, agent, or prompt fits. Cost, reliability, and output quality become measurable. There’s also a side effect: private benchmarking. This kind of visibility creates internal insights most teams don’t have. We already know companies do this quietly, and that information has real value. We’re still early. For now, we run agents, observe behavior, change one variable, and run again. If you’re running autonomous workflows, we love to hear where your biggest pain points are and see if we can help refine the process. (below an example we did on optimising a marketing workflow for content creation)
2
3
98