Pilot overview
Your strategy.
The data it needs.
Musashi started as an X extension that displayed matching prediction markets under tweets. We’re exploring delivery of that matching capability as structured data for agent builders.
Start with one use case
Tell us what your agent does, which sources and markets matter, and what your current providers miss. We’ll discuss available data, delivery requirements, and a sample that could demonstrate value.
From browser cards to software
The extension source is available on GitHub. It extracts tweets, calls a matching API, and injects market cards. Its backend is currently paused. The proposed feed changes the customer, input collection, and delivery; it is not an already operating B2B service.
Explore the visual comparison →
The $200 sample pilot
A one-time USD $200 pilot covers one agreed use case, up to 25 customer-supplied public posts or headlines, a matched-market JSON sample, and one feedback round. Scope, suitable data access, and timing are confirmed before payment. There is no checkout or automatic subscription.
The sample pilot does not include continuous source collection or hosted API access. Production pricing is quoted separately based on sources, volume, and delivery requirements. The feed is still proposed.
What a record could contain
| Field | Purpose |
|---|---|
source | Original text, source URL, and publication time. |
related_markets[] | Venue, contract identity, question, and the connection to the source. |
relationship | Whether the story addresses the condition directly or supplies related context. |
context, caveat | An explanation of the link and limits of the available information. |
Inspect one illustrative record
{
"demo": true,
"schema_version": "0.1-proposed",
"id": "demo-policy-001",
"topic": "Policy",
"source": {
"kind": "social_post",
"label": "Illustrative social post",
"text": "White House proposes higher tariffs on imported vehicles.",
"url": null,
"published_at": null
},
"related_markets": [
{
"venue": "Polymarket",
"market_id": null,
"url": null,
"question": "Will the US announce new auto tariffs this quarter?",
"relationship": "direct",
"context": "The proposal concerns an announcement. Final contract rules would need to establish what qualifies."
},
{
"venue": "Kalshi",
"market_id": null,
"url": null,
"question": "Will higher auto tariffs take effect this quarter?",
"relationship": "context",
"context": "A proposal is related news, but does not establish that tariffs have taken effect."
}
],
"caveat": "A proposal is not implementation."
}Agree what success means
Before a pilot starts, we agree on scope, data access, a way to evaluate matching quality, and delivery expectations. We want to establish whether the output improves your actual workflow.
Where things stand
This website is an interactive product concept. Demo headlines and contracts are fictional; exchange names identify intended venues, not partnerships or verified integrations. There is no live feed, public endpoint, SDK, or guaranteed delivery schedule yet. The JSON shape is illustrative and may change.
We’re looking for pilot collaborators to shape the first useful version. Any production collection, processing, or delivery would be scoped separately. The demo makes no claims about speed, predictive accuracy, or trading returns.