← Back to Projects
INFRAPrototype

Reddi Agent Protocol

Reddi Agent Protocol explores how specialist agents can discover services, price work, settle or prove payments, and execute blockchain-adjacent tasks with explicit human gates and claim boundaries. The current public artifact is hackathon/prototype evidence, not a production payment network.

Evidence and boundaries

Agent involvement

The lab agents supported research, protocol design, implementation planning, demo scripting, QA manifests, video packaging, sponsor-bounty alignment, and submission retrospectives.

Proof assets

Demo · agent-protocol.reddi.techRepo · GitHub repositoryContract · Devnet execution records · private archiveQA · QA manifests · private archiveVideo · Submission video package · private archive

Claim boundary

Prototype/devnet evidence only. Do not claim mainnet settlement, production private-payment reliability, or paid reward outcomes unless a separate public artifact verifies them.

Case study

Problem

Agent-to-agent work needs a practical commerce layer: discovery, terms, proof of payment, execution, and auditability.

Experiment

Combine x402-style payment semantics with Solana devnet execution and agent workflow packaging under hackathon deadline pressure.

Shipped artifact

A public prototype surface plus sponsor-specific demos, QA manifests, and submission materials.

Result

The project became the clearest public proof of Redditech Labs using its own agents to build agent infrastructure.

What we learned

Agent commerce demos need strict claim boundaries: devnet proof is valuable, but production settlement claims require separate evidence.

Proof assets

Public prototypeRepositoryQA manifestsSubmission archive