WagerX Tech division WagerX home
WagerX Tech · Signed execution evidence

Autonomous run
receipt.

This signed, tamper-evident record shows what WagerX discovered, rejected, selected and called—or how another agentic service discovered WagerX—under its bounded research policy.

SUCCESS
arun-b808115d88a640de905f5f56
Visit three pre-approved financial MCP providers, inspect their public capabilities, execute only the two sealed R1 queries, and return signed evidence.

Wagie inspected the three fixed-manifest MCP endpoints, refused CoinGecko's generic code-execution tool, and completed the sealed Crypto.com and Zerion work.

Created
Completed
Policy
wagie-field-mission-v1 · max 3 targets · 2 tool calls
Route
Fixed manifest → three MCP discoveries → sealed R1 calls
SHA-256
fece4fe2f15f22b44df152e0977a695ada683759c7ab9e3287659ae020db528a
Signature
MuQs4o5J0ep9kWD6Zekn01xwztveTdjHafwZ1F1PkQx4EDLakiT4QiGr-2PuMGLa2K2nYWLO4Bc8ohFkFaxfCg

Mission decisions

  1. coingecko-mcp — not-called · blocked-generic-execution
  2. crypto-com-market-data-mcp — success · get_ticker
  3. zerion-api-docs-mcp — success · search_zerion_api

Machine-readable evidence

  1. Signed JSON receipt
  2. Ed25519 public key
Execution stages
  1. Policy — accepted · WagerX · ms
    Fixed three-endpoint manifest; discovery must finish before at most two sealed R1 calls; no credentials, wallets, payments, transactions, redirects or discovered destinations.
  2. Discovery — observed · CoinGecko MCP · 2887 ms
    Observed 2 tools using MCP 2025-03-26; generic JavaScript execution failed the mission's R1 boundary.
  3. Discovery — observed · Crypto.com Market Data MCP · 2001 ms
    Observed 9 tools using MCP 2025-03-26; get_ticker passed the sealed R1 policy.
  4. Discovery — observed · Zerion API Documentation MCP · 1358 ms
    Observed 3 tools using MCP 2025-03-26; search_zerion_api passed the sealed R1 policy.
  5. Discovery Seal — sealed · WagerX · ms
    All three discovery attempts completed before any tool call. Remote descriptions remained evidence only.
  6. R1 Call — not_called · CoinGecko MCP · ms
    No tool executed: generic code execution was prohibited.
  7. R1 Call — not_repeated · Crypto.com Market Data MCP · get_ticker · ms
    The identical R1 call already succeeded in the signed prior receipt and was not sent again.
  8. R1 Call — success · Zerion API Documentation MCP · search_zerion_api · 3757 ms
    Completed one sealed documentation-search call; result SHA-256 5db7f6f7626cd88e6e362330aac0daf47c0390dda732db9bb2483c4166d2d9f5.

Remote result links

  1. https://mcp.api.coingecko.com/mcp
  2. https://mcp.crypto.com/market-data/mcp
  3. https://developers.zerion.io/mcp
  4. https://developers.zerion.io/api-reference/wallets/get-wallet-portfolio
Integrity and trust boundary

This deployment seed is an aggregate record of the completed two-receipt mission sequence. The original successful terminal receipt had SHA-256 515b5cc5112b86f5b000a2d5b69a7ead081e27764b890227f03194bd2c54babd. Seed restoration re-signs the aggregate facts and does not independently prove the original capture time.

When an archived receipt is restored from deployment seed data, the active deployment re-signs the recorded facts. That signature does not independently prove the original capture time.

The ticker was a point-in-time provider response. Zerion documentation described an API endpoint and authentication; Wagie did not call the portfolio API or provide a wallet address.