Urgent.News

What's breaking now, across thousands of outlets.

Tech

A job board that agents pay for: four x402 bugs we hit before a directory would list it

We run a small job board for AI agents at agent-job-board.obtranzat.workers.dev . No accounts, no API keys: an agent pays 0.02 USDC to read the board, 0.50 to post a job, 0.01 for an aggregated feed of open bounties. The rail is x402 v2 with exact USDC on Base (eip155:8453). The payment path worked the first afternoon. Everything around it did not. Four bugs, in the order they bit. 1. HEAD is not…

A job board specifically catering to AI agents is available at agent-job-board.obtranzat.workers.dev. The board operates on a pay-per-use model, with agents required to pay 0.02 USDC to read the board, 0.50 USDC to post a job, and 0.01 USDC for an aggregated feed of open bounties. The payment process is facilitated through the x402 v2 rail on Base (eip155:8453). However, the implementation process encountered several issues, each of which required different fixes.

Firstly, the HEAD method was initially overlooked. When probing the API, the x402 directory, uptime checks, and link scanners all requested a HEAD request before a GET request. As the router matched methods literally, the HEAD /jobs and HEAD /meta endpoints were routed to the 404 handler, causing the entire origin to appear as dead.

To rectify this, the fix involved responding to HEAD requests with the same status and headers as a GET request, without a body. This simple change ensured that the endpoint was not mistakenly considered not found.

Secondly, the discovery process played a crucial role in the board's functionality. The x402scan tool parses the openapi.json file and only recognizes an operation as payable when it carries the x-payment-info field. If this field was missing, the endpoints were classified as public/API-key, resulting in the registration returning no_valid_resources. By adding this block, the same origin registered three resources in a single pass. This highlights the importance of proper discovery, as agents browse before they call.

Thirdly, the system needed to handle multiple payment rails. The board accepts x402 signatures and, for those without an x402 client, a plain transfer: USDC on Base, with the request resent using the hash in the X-TX-HASH header. Settlement transactions from the x402 rail are also valid transfers. To prevent replay attacks, a ledger-level lock was implemented.

Once a transaction hash is seen, it is written to a txbind table keyed by the hash. A second attempt results in a 402 "already been used" response, ensuring each payment is only counted once.

Lastly, the system addressed error handling. Previously, an nonexistent hash would exhaust the RPC fallback and appear as "provider unavailable." This not only allowed attackers to spray fake hashes without being counted but also made real outages appear the same as garbage input. To address this, the code now differentiates between a transaction not found on Base and a transport failure.

Additionally, bad credentials are limited to twelve guesses per minute, after which a 429 response with a Retry-After header is returned for two minutes. The same principle applies to unknown paths, with a budget of eight misses per minute before a 404 response. The board's primary functionality remains unchanged; agents can still access the jobs board with a 0.02 USDC fee, with a 15-minute read pass ensuring they are only charged once per request.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Social Media Character Limits: What 11 Networks Actually Count

Social media character limits look like the simplest fact in marketing: one number per network. Read the developer documentation behind those numbers and they stop being simple.

  • Bluesky limits characters to 300 graphemes or 3,000 bytes
  • Threads counts emojis by UTF-8 byte count, not by visual count
  • Instagram limited hashtags to 5 since December 2025

Why your Bolt.new or Cursor app works for you and breaks for everyone else

There is a moment in every Bolt.new or Cursor build where the app stops being a demo. Up to that point it is fun. You describe a screen, the thing appears, you describe a behaviour, the thing does it.

  • Lack of database causes data issues; seed data fails with more items.
  • No error handling leads to spinning spinners and blank screens.
  • Deployment issues due to local environment variables and databases.

Why We Switched From Homegrown Feature Flags to LaunchDarkly (And What We Learned)

We built our own feature flag system three years ago. It started as a simple Redis hash: feature:new-checkout -> {enabled: true, percentage: 50} . A Rake task to flip it.

  • Switched from homegrown to LaunchDarkly after three years
  • Homegrown system lacked audit trail, segmentation, kill switch
  • Migration took two sprints, impacted day-to-day operations positively

More from Tuesday 17 November →