RaidGuild CohortRaidGuild Cohort
Public

Bring your own agent: inside RaidGuild’s commerce matchmaking experiment

Author

Date Published

Concept illustration of two angular robotic brokers and a human merchant exchanging offers in a lantern-lit industrial bazaar.

A member has something to sell. Another member is looking for it. Can their agents help them find each other and start a negotiation? RaidGuild’s November cohort is building a small commerce experiment to explore that interaction.

The matchmaking network, currently using the working name Matchmaker, has an initial MVP available to RaidGuild members through the Portal. It gives the cohort something concrete to try while we work out which parts of commerce are useful to hand to an agent.

Watch the commerce experiment video on YouTube

A listing, with help from your own agent

Santiago introduced the MVP in the cohort’s working thread on November 11. Members can use the app to post listings, browse items, and begin negotiating. They can also connect an agent through the app’s Agents section, which provides a scoped access token and a prompt template.

An early test followed that path. Dekan logged in through the Portal, created an agent key, and pointed his personal agent at the service. After receiving the key, the agent walked him through making a listing. He then invited other members to add test items so he could try matching.

That report gives us a useful starting point: a member connected an existing agent and used it to create a listing. It does not yet establish a completed match, negotiation, or sale. Those are interactions for the pilot to test and document.

Where the current experiment stops

The storefront and matchmaking network explore different interactions. The storefront provides a direct buying experience. The matchmaking network explores discovery and negotiation between parties, with the option to bring an agent into that process.

In the current scope described by the build team, the network makes the match and hands the actual deal to the two parties. Payment handling is a separate question. A listing or a match should not be read as proof that payment or fulfillment has happened.

Keeping that boundary visible helps us test the interaction we have before adding more responsibilities. Can members describe what they want? Can an agent help represent an offer? What information do both parties need before agreeing on a deal?

Questions for the next iteration

The working discussion has already surfaced several directions. Payment requests and receipt verification could become adapters. Listings might eventually be imported from the RaidGuild storefront or other marketplaces. The team is also discussing whether reputation should belong to an agent, its human operator, or some combination.

These are design questions, not features we are announcing. The same applies to monetization: fees, hosted community networks, and proactive matching have been raised as possibilities, but no model is settled. Even the name is still being discussed.

Help us test the next interaction

The initial buying and selling audience is primarily RaidGuild members. The cohort is also an invitation to contribute to the build: try the member app, help test a workflow, improve the interface, or document what happens.

For a useful test, bring a clear offer or request. If you are using test items, label them as tests. Record where the interaction works and where someone needs to step in. A confusing permission prompt or a stalled negotiation is useful feedback too.

This build update is one step toward a fuller case study. We want to document the decisions and real interactions that make the experiment worth learning from.

Explore the November cohort and how to participate

Open the matchmaking module — Portal member access required

Have a project in mind?

Start a conversation with RaidGuild

Tell us what you are building and where the guild could help.

Make a general inquiry

Comments

No comments yet.

Log in to leave a comment. Log in