What is Crosswire?
A matching title or strike does not establish equivalent settlement. A contract may use another price index, closing instant or cancellation rule. Crosswire fits between pair discovery and execution, returning a structured verdict and findings about these differences rather than forecasting which outcome will win.
Coverage discovery supplies supported event and pair identifiers. REST and MCP expose the audit for code and agents, and free covered examples provide an integration starting point. A verdict applies to the inspected pair and snapshot: it is neither universal matching coverage nor an instruction that places either leg of a trade.
Who it is for
- Developers building strategies across prediction venues.
- Researchers auditing the rules of matched event contracts.
- Agents needing structured reasons to reject a proposed market pair.
Features and coverage
- Rule comparison
Compare the oracle or source, settlement instant, event scope and conditions that can void a contract.
- Verdict and findings
Read SAFE, CAUTION or BLOCK alongside individual findings and severity fields. A label should not replace inspection of the reported differences.
- Audit record
The response identifies both legs, match confidence, rule flags, snapshot age and ruleset hash.
- Coverage discovery
List supported events and pair identifiers before requesting an audit; coverage is limited to those listed pairs.
- REST and MCP access
Call the audit route from code or use coverage-discovery and resolution-risk tools through an MCP client.
- Metered crypto access
The crypto inventory uses x402 payments on Base. Public example pairs let developers inspect the response before enabling paid calls.
Workflows with Crosswire
Audit a proposed hedge
Resolve the pair to supported market references, request the audit and examine every divergence. Feed both the verdict and detailed rule findings into the strategy’s eligibility decision.
Retain the decision context
Keep the audit result attached to the decision it informed. Leg identifiers, findings, snapshot age and the ruleset hash let a later reviewer identify the contracts and rule version behind that decision.
Start with a covered example
Use a free supported pair to inspect the full response shape and confirm handling of findings and data age before enabling metered requests.
Pricing and total cost
The published metered audit price is US$0.02 per call, paid in USDC on Base through x402.
Access: Covered World Cup example pairs are free to audit. Consult the coverage list for the required event family and access route.
Getting started
Before you start: Coverage is restricted to listed event pairs.
- Read coverage and obtain canonical event or pair identifiers.
- Choose the REST audit route or MCP connection.
- Inspect the complete response using a covered free example.
- Handle verdicts, individual findings and data age in the integration.
- For metered crypto calls, configure an x402-compatible payment client and an explicit request budget.
Only listed event pairs are covered; Crosswire is not a universal contract matcher.
Useful links
What to check
- Coverage is restricted to listed event pairs.
- The service returns settlement-compatibility data and does not execute either trading leg.
- A semantic match and fee-adjusted spread do not cancel a flagged timing or void-rule difference.
A closer look
Ratings & reviews
User reviews 0
The main score switches to user ratings after 5 published reviews.
A specific example helps the next person choose the right tool.
Related tools
Browse categoryFrequently asked questions about Crosswire
What can an audit reveal?
Contracts with similar names may use different settlement sources, times, event scopes or cancellation rules. The findings identify those divergences.
Can an agent use Crosswire?
Yes. MCP exposes coverage discovery and resolution-risk checks.
Does the verdict forecast the winner?
No. It compares the contracts and their rules rather than predicting the outcome.
What should accompany a saved result?
Keep the leg identifiers, individual findings, snapshot age and ruleset hash so the decision retains its audit context.


