I agree with Dario that we need to pace the frontier. This has been a primary topic of discussions we've had at OpenAI in recent weeks.
Committing to having independent evaluators with employee-like access is a great idea, and we will do the same. We'll have more to share soon.
Seeing an uptick in usage on @Nitrograph since Grok Bot Launch.
One API, 10,000+ Services. Grab your API key, give it to your Grok Bot, and take it for a spin.
Also works with every other harness, and has extensions in app store for ChatGPT and Claude.
Everyone thinks AI is creating a bubble.
Meanwhile there has never been more contracted demand for infrastructure in human history.
Dot com bubble was the opposite. Built the supply, prayed for the demand. Most of it sat dark for a decade.
AI inverted it. The demand is signed and screaming. Chips allocated years out. Data centers leased before ground breaks. Turbines sold out into the 2030s.
2000: price above value. A bubble.
2026: demand above capacity. A bottleneck.
Bubbles pop. Bottlenecks get paid.
It gives agents a place to coordinate, delegate, execute, and operate as a system. Not merely exchange messages. The difference is not incremental. It is an order of magnitude larger than what conventional (pre AI) communication platforms were built to support.
@0xfishylosopher@jonah_b We've built a discovery layer for agents, and based on how agents are using it, what machine payments unlock are workflows.
The UI will be the workflow, you're not constrained by SaaS token limits & monthly subs. Just your budget.
Our initial strategy is akin to PageRank
@useapolloio@tempo Yep! Great for basics, but you canโt tune skills and chain steps quite as well as in CLI. Harness can also do much more once your list is built on the GTM side ๐
Plus, can build monster lists outside constraints of subscriptions and tokens with MPP.
We turned one market thesis into 905 enriched contacts across 256 accounts.
Not by buying another GTM subscription.
Not by spending a day clicking filters in Apollo or Clay.
Claude Code did the GTM engineering.
@useapolloio supplied the data.
@tempo / MPP gave us usage-based access.
This is where GTM is going.
This is why we are releasing a local GTM agent harness that turns a natural-language market attack into:
- target companies
- enriched contacts
- ranked accounts
- rejection logic
- attack cohorts
- messaging angles
- campaign-ready exports
No bloated stack required.