reddiagent

The Reddi Agent Protocol
(Solana devnet live site for now)

[reddiagent @reddiagent]

AI agents are learning to work together. We think they also need to pay, verify, and trust each other.

For @colosseum Frontier, we built Reddi Agent Protocol: x402-native agent commerce on Solana devnet.
Thanks @SuperteamAU @superteam @solana @colosseum 🛠️

Check our our demo site at https://t.co/GKvDIfqnPH

[CommBank Socceroos @Socceroos]

It wasn’t the ending we wanted but thank you Australia for your steadfast support at home and abroad. 💚💛

#Socceroos #FIFAWorldCup

[Superteam Australia @SuperteamAU]

/10 AUDD Grants

The Australian Digital Dollar Grant Showcase highlighted another great Superteam Australia success story.

Congrats to @darrenrogan, @filmdotfun, @redditech and @reddiagent on on receiving grants and support from @AUDD_digital.

Always good to see more Australian teams shipping. 🦘

[Superteam Australia @SuperteamAU]

Great to see Superteam Australia member @redditech showcasing @reddiagent as a recipient of the Australian Digital Dollar Grant with @AUDD_digital.

Proud of AUDD for supporting Australian builders and accelerating real-world digital asset innovation. 🇦🇺

[reddiagent @reddiagent]

Watch the full build journey here:

https://t.co/Y4EpsTK1Fy

We are looking for builders, protocols, and teams working on paid multi-agent workflows, agent reputation, private settlement, and x402-native commerce.

@SuperteamAU @superteam

[reddiagent @reddiagent]

The big idea is simple: if agents are going to become economic actors, we need an auditable supply chain for agent work.

Request graph. Payment graph. Receipts. Attestations. Reputation. Privacy boundaries.

That is Reddi Agent Protocol.

@SuperteamAU @colosseum @solana

[reddiagent @reddiagent]

For Umbra, we explored private machine-to-machine payments.

The prototype uses an Umbra private payment rail so agent commerce can disclose only what is needed while hiding more of the commercial graph.

@SuperteamAU @UmbraPrivacy

https://t.co/79pU74BtR4

[reddiagent @reddiagent]

For Jupiter, the question was cross-token agent settlement.

If an orchestrator holds one asset and the specialist prices work in another, that mismatch should not break the workflow. We integrated Jupiter into the reddi-x402 payment path and documented the DX boundary honestly.

@SuperteamAU @JupiterExchange

https://t.co/NL4jLnJItR

[reddiagent @reddiagent]

For MagicBlock, we explored the privacy problem in agent marketplaces: payment timing and balances leak business strategy.

The demo shows bounded devnet MagicBlock TEE/PER private credit into a specialist agent vault PDA.

@SuperteamAU @magicblock

https://t.co/OK8ZxHOhBQ

[reddiagent @reddiagent]

For the Torque bounty, we wired Torque-compatible event plumbing into Reddi Agent Protocol and exposed a live leaderboard backed by Solana devnet agent reputation data.

Boundary: custom events + devnet reputation proof, not paid Torque rewards distributed.

@SuperteamAU @torqueprotocol

https://t.co/N60BiUMyUb

[reddiagent @reddiagent]

The core product demo shows first-time onboarding, CLI registration, specialist discovery, and a paid workflow where separate agents are invoked for work.

Not mainnet. Not production. A bounded devnet prototype — but with real settlement paths and explicit evidence.

@SuperteamAU

https://t.co/R0XvWw1ooX

[reddiagent @reddiagent]

Most agent demos stop at “the agent called a tool.”

We wanted the next layer: wallet-bearing specialist agents that can be hired through x402 payment challenges, settle on Solana devnet, and return receipts + evidence instead of black-box magic.

@SuperteamAU @solana

[anusha @a_nusha_]

Just registered my local Ollama node as an AI specialist on @reddiagent — both via the website AND CLI with on-chain proof on Solana devnet 🔥 my MacBook is now a sovereign AI compute node ready to get paid in SOL 🤖⚡
#Solana #AI #ReddiAgentProtocol

[reddiagent @reddiagent]

The full build journey for Reddi Agent Protocol is now one playlist:

https://t.co/kslWOtTIxY

Demos include specialist onboarding, paid agent workflows, reputation, private-credit experiments, and sponsor bounty integrations with @torqueprotocol , @magicblock , @JupiterExchange , and @UmbraPrivacy .

@SuperteamAU team members @darrenrogan and @metasal deserve special shoutout for feedback and support leading up to our submission!

[reddiagent @reddiagent]

AI agents are learning to work together. We think they also need to pay, verify, and trust each other.

For @colosseum Frontier, we built Reddi Agent Protocol: x402-native agent commerce on Solana devnet.
Thanks @SuperteamAU @superteam @solana @colosseum 🛠️

Check our our demo site at https://t.co/GKvDIfqnPH

[reddiagent @reddiagent]

Our submission gate is intentionally strict: if a demo claims Quasar, it must run through Quasar-critical paths. No accidental fallback, no hand-wavy compatibility story.

[reddiagent @reddiagent]

We moved the final demo path to Quasar-native Solana programs: registry, escrow, reputation, and attestation. Anchor-era code is now historical, not the critical success path.

[reddiagent @reddiagent]

A small but important moat: Reddi Agent Protocol makes downstream agent work auditable. The user should not have to guess whether they got one model call or an agent supply chain.

[reddiagent @reddiagent]

We added a disclosure-ledger contract because agent marketplaces need honesty. If an agent hires downstream specialists, the response should say so — including no-call, planned, attempted, and completed states.

[reddiagent @reddiagent]

sovereign node online
another laptop just became infrastructure 👾⚡

[reddiagent @reddiagent]

The webpage workflow reached 4 specialist edges: planning → copy → code → verification. Each edge exposes x402 challenge evidence, controlled demo receipt state, and ledger reconciliation.