OracleNet: 6 oracles / 62 MCP tools now ANP-discoverable with DID:WBA identities

[ToolOracle]

Title (paste into title field):

OracleNet: 6 oracles / 62 MCP tools now ANP-discoverable with DID:WBA identities

Body (paste below):

We operate OracleNet — an M2M agent mesh with 91 MCP-based oracles and 589 tools across compliance, finance, blockchain, travel, compute, and geo domains.

Over the past few days we implemented ANP compatibility for 6 of our oracles as a pilot. All of this is live and externally verifiable right now.

What we built

DID:WBA identities for 6 oracles, generated via agent-connect SDK (v0.3.7):

• did:wba:tooloracle.io:weather — 10 tools (current weather, forecasts, air quality, marine, historical)
• did:wba:tooloracle.io:flight — 8 tools (schedules, pricing, airport status)
• did:wba:tooloracle.io:hotel — 8 tools (search, availability, pricing)
• did:wba:tooloracle.io:gpu — 12 tools (Vast.ai GPU pricing, A100/H100/RTX availability)
• did:wba:tooloracle.io:crypto — 12 tools (prices, market data, exchange rates)
• did:wba:tooloracle.io:map — 12 tools (geocoding, routing, distance calculations)

ANP Discovery Protocol (Spec 08) index at:

https://tooloracle.io/.well-known/agent-descriptions

Returns a JSON-LD CollectionPage with all 6 oracles. Content-Type: application/ld+json.

Agent Description documents (Spec 07) for each oracle, e.g.:

https://tooloracle.io/weather/agent-description.json

Each description lists multiple parallel interfaces:

• MCP — standard JSON-RPC 2.0 endpoint
• MCP+x402 — pay-per-call USDC micropayments on Base (~$0.01/unit)
• MCP+ANPAuth — DID:WBA cryptographic authentication (currently enabled on weather)
• Handshake — LLM-routed natural-language first-contact endpoint

DID:WBA authentication proxy on WeatherOracle (/weather/anp/mcp/):

• Client signs requests with their DID private key
• Server fetches client's DID document from their domain and verifies signature
• Replay protection via nonce cache
• Cross-server auth tested over public internet

Natural-language handshake endpoint at https://tooloracle.io/handshake:

• POST {"intent": "I need GPU pricing for an H100"}
• Returns JSON-LD routing recommendation with oracle name, DID, available interfaces
• Classification powered by Gemma 4 26B running locally

How to verify

from agent_connect.authentication.did_wba import resolve_did_wba_document_sync

doc = resolve_did_wba_document_sync("did:wba:tooloracle.io:weather")
print(doc["id"])  # did:wba:tooloracle.io:weather

Or:

curl -s https://tooloracle.io/.well-known/agent-descriptions | python3 -m json.tool
curl -s https://tooloracle.io/weather/did.json | python3 -m json.tool

Observations during implementation

1. DID resolution path: We initially placed DID documents at /{path}/.well-known/did.json but the SDK resolves did:wba:host:path to /{path}/did.json (no .well-known for sub-paths). Might be worth calling this out more prominently in the getting-started guide.

2. Auth header prefix: generate_auth_header() returns the value with the DIDWba prefix included. verify_auth_header_signature() also expects the prefix. This caused a subtle double-prefix bug when we naively prepended DIDWba ourselves. A note in the docstring would save others the same debugging session.

3. MCP + ANP coexistence: Our oracles serve MCP natively. We added ANP as an additional identity/discovery/auth layer without replacing MCP. This seems like the natural adoption path for existing MCP tool providers — interested in your thoughts on whether this aligns with ANP's vision.

4. Application-layer protocol contribution: We operate in a specific domain (EU regulatory compliance — MiCA, DORA, AMLR) with cryptographically signed evidence as the primary service. Would an application-layer protocol spec for compliance evidence exchange between agents be a useful contribution to ANP?

About us

ToolOracle is the M2M agent infrastructure brand of FeedOracle Technologies, based in Germany. We run 91 MCP oracles with approximately 15,000 MCP calls/day in production. The ANP integration was built using agent-connect 0.3.7 and follows Specs 03 (DID:WBA), 07 (Agent Description), and 08 (Discovery).

Happy to share technical details, anonymized traffic patterns, or collaborate on interoperability testing.