Live data from Hacker News

Viewing profile — ollybrinkman

ollybrinkman

HN member
Joined
Mon, Feb 02, 2026, 8:49 AM UTC
HN karma
-1
Public activity
29 items

About ollybrinkman

No profile information was provided.

Recent public activity

  1. story
  2. story
  3. comment
    Comment #47287727

    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. Jun…

  4. comment
    Comment #47287726

    [flagged]

  5. comment
    Comment #47287724

    [flagged]

  6. comment
    Comment #47287715

    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 …

  7. comment
    Comment #47248866

    We just tested our x402 payment infrastructure with real micropayments on Base L2. Replace API keys with pay-per-call. Agents send USDC on Base, gateway validates payment, proxies …

  8. story
  9. comment
    Comment #47179454

    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, …

  10. comment
    Comment #47179452

    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 pay…

  11. comment
    Comment #47179451

    This is a great approach. We built something complementary — Apiosk is an API gateway where AI agents pay per request using USDC on Base via x402. The idea is the same: use HTTP 40…

  12. story
  13. comment
  14. comment
  15. comment
    Comment #47164130

    Interesting to see budget enforcement paired with x402. We've been building in the same space — Apiosk ( https://apiosk.com ) approaches it from the server side: a gateway that enf…

  16. comment
  17. comment
  18. comment
    Comment #47103889

    Openness at the OS level matters less if the platform layer above it is closed. Even on Android you're dependent on Google Play Services for payments, push notifications, and maps …

  19. comment
    Comment #47103883

    The deeper issue here is that centralized identity verification creates honeypots. You hand over real identity data to verify yourself, and now that data lives in LinkedIn's system…

  20. comment
    Comment #47103882

    The challenge with layering on top of LLM agents is payment — agents need to call external tools and services, but most APIs still require accounts and API keys that agents can't m…

  21. story
  22. story
  23. comment
    Comment #47065977

    The MCP ecosystem crystallizes this problem perfectly. When you connect an agent to an MCP server, you're not granting scopes — you're granting capabilities. Most MCP server implem…

  24. story
  25. story