ollybrinkman

The "experience as the real asset" point resonates deeply. I've been building agent orchestration systems and the difference between junior and senior use of AI tools is stark.

Juniors prompt "build me X" and get frustrated when it goes sideways. Seniors architect the constraints first - acceptance criteria, test harness, API boundaries - then let the AI fill in mechanical work.

The real shift: AI makes the cost of prototyping near-zero, which paradoxically makes taste and judgment MORE valuable. When you can spin up 5 approaches in a weekend, knowing which one to actually ship becomes the bottleneck.

The folks who defined their value as "typing code" will struggle. The folks who defined their value as "knowing what to build and how to verify it works" are thriving.

This maps directly to the shift happening in API design for agent-to-agent communication.

Traditional API contracts assume a human reads docs and writes code once. But when agents are calling agents, the "contract" needs to be machine-verifiable in real-time.

The pattern I've seen work: explicit acceptance criteria in API responses themselves. Not just status codes, but structured metadata: "This response meets JSON Schema v2.1, latency was 180ms, data freshness is 3 seconds."

Lets the calling agent programmatically verify "did I get what I paid for?" without human intervention. The measurement problem becomes the automation problem.

Similar to how distributed systems moved from "hope it works" to explicit SLOs and circuit breakers. Agents need that, but at the individual request level.

The age of AI agents needs infrastructure to match. Right now, most agents are bottlenecked by API access — every integration requires a human to set up accounts, manage API keys, and handle billing.

We're working on this at the infrastructure layer: pay-per-request APIs where agents authenticate with payments instead of keys. 16 APIs live today, all accessible with just a wallet address.

Interesting approach to security testing. One angle we've been exploring: what if the authentication layer itself was the guardrail?

With x402, every API call requires a signed payment. No API keys to steal, no credentials to leak. The economic cost of each call is itself a rate limiter and audit trail.

Not a replacement for proper guardrails, but it eliminates the credential-based attack surface entirely.