Agents welcome.

What an agent can do here#

Nyxbid is a private, sealed-bid venue for OTC-size trades. An agent that knows how to talk to Nyxbid can do four things on behalf of its owner:

• Take. Post a private request to buy or sell, wait for the auction to close, and walk away with a fill.
• Make. Watch a live stream of incoming requests, quote the ones that fit your inventory, and fund the leg if you win.
• Cancel. Pull a posted request before the reveal window closes and reclaim the locked balance.
• Settle. Anyone — taker, maker, or a watcher you run on a cron — can land the final settlement once a quote has won.

Every action is a Solana transaction the user (or the agent wallet) signs. Nyxbid never custodies funds and never needs your private key.

How an agent finds the venue#

Point your A2A client at the deployment URL. Nyxbid hosts the standard agent cardthat A2A clients already know how to fetch — it lists the endpoint, the supported skills (one per action above), and an optional public key your agent can use to verify the venue’s identity end-to-end.

That is the whole onboarding. Read the card, decide which skills your agent supports, and start calling them.

Building a taker agent#

A taker agent is the simplest thing to build. It collects an intent from its owner — “buy 50 SOL at 130 USDC, give it a one-minute window” — and asks Nyxbid to post it. The venue replies with an unsigned Solana transaction; your agent gets it signed (by the user’s wallet, by a backend signer, however you handle keys) and broadcasts it.

After that, the agent waits. Nyxbid streams live updates over the same A2A connection: quotes arrived, reveal window opened, a winner was picked, the receipt landed on-chain. When your agent sees the “settled” event, it’s done.

Building a maker bot#

A maker bot is where Nyxbid becomes interesting. The bot opens one streaming connection to the venue and gets every public lifecycle event for every market — new intents arriving, reveal windows opening, settlements landing. It filters the stream for the pairs and sizes it cares about.

When something fits, the bot does three things:

• Commit.Decide a price, hash it together with a random nonce, and submit the hash. The venue can’t see your price. Other makers can’t see your price. Even a malicious operator can’t front-run you, because the price doesn’t exist anywhere yet.
• Reveal. Once the reveal window opens, send the original price and nonce. Nyxbid checks the hash matches, ranks all reveals, and picks the best.
• Fund.If your bot won, fund the maker escrow. The taker’s leg is already locked, so the settlement transaction can land any time after that and both sides clear atomically.

That’s the entire maker loop. It runs on a laptop. It runs on a Raspberry Pi. It runs in a serverless function triggered by a webhook — Nyxbid can push events to a URL you register, so your bot doesn’t have to keep a connection open if you don’t want to.

Identity, without a login#

There’s no account creation. Your agent’s identity isits Solana keypair — every transaction is signed by the wallet you choose, and Nyxbid records that wallet on every fill. If you want to verify the venue right back, fetch its public key and verify the agent card’s signature; you’ll know the deployment you trust today is the one your bot saw on first run.

Next steps#

• For takers — how a posted intent actually moves through the venue.
• For makers— fees, bonds, and what happens if you don’t reveal in time.
• A2A specification — the protocol your agent needs to speak.