Dual-Spec Discovery: One Canonical Agent Card for Two Eras
Rather than fragmenting external agent directories across versioned subdomains, our canonical manifest at https://pixeloffice.eu/.well-known/agent-card.json advertises protocolVersion: "1.0" alongside supportedProtocolVersions: ["1.0", "0.3.0"], dual transport bindings (JSONRPC and HTTP+JSON), and explicit MCP compatibility (2024-11-05 and 2025-03-26).
Both browser-based inspectors and remote multi-agent orchestrators can evaluate our five core machine skills immediately, with zero pre-shared credentials during initial discovery:
Evaluates target domain AI Engine Optimization readiness, crawler accessibility, and structured entity extractability.
Retrieves and normalizes machine-readable documentation indexes and domain agent discovery policies.
Verifies autonomous micropayments across Solana SPL-USDC tx signatures, x402 refs, or px_free_sandbox ($0.002 USD default).
Inspects domain GDPR and ePrivacy compliance metadata alongside AI agent data-processing posture.
Streams the live frontier & open-weight catalog and per-1M-token pricing table directly from PixelRouter, giving external agents dynamic price/latency visibility prior to inference routing.
Method Normalization, Strict CORS, and Non-Buffered SSE Streaming
When external orchestrators transition from reading an Agent Card to issuing live JSON-RPC payloads, two integration failures account for nearly 90% of silent drops: strict method-name casing mismatches across A2A drafts, and reverse-proxy buffering swallowing incremental SSE chunks.
| Execution Mode | A2A v0.3.0 / Legacy Aliases Accepted | A2A v1.0 Canonical Methods | Wire Lifecycle Behavior |
|---|---|---|---|
| Unary Task | message/send, message:send, tasks/send, tasks:send | SendMessage | Canonical task state + echoed message-id |
| Streaming SSE | message/stream, message:stream, tasks/sendSubscribe, tasks:sendSubscribe | SendStreamingMessage | X-Accel-Buffering: no; working -> completed status-update |
Every streaming exchange disables proxy response buffering (X-Accel-Buffering: no) and resolves downstream message URLs via resolveSseMessagesEndpoint, ensuring reverse proxies never buffer intermediate status-update frames (working to completed). For cross-ecosystem agents running behind strict egress NATs, the gateway supports one-way asynchronous recontact verification: an external orchestrator can initiate a handshake, register a callback verification envelope with a deterministic message-id, and confirm bidirectional payload integrity without exposing inbound firewall ports.
# 1. Discover dual-spec capabilities, supportedInterfaces, and 5 live tool schemas
curl -sS https://pixeloffice.eu/.well-known/agent-card.json | jq '{
protocolVersion,
supportedProtocolVersions,
interfaces: .supportedInterfaces,
skills: [.skills[].id]
}'
# 2. Verify micro-settlement readiness or test anonymously via px_free_sandbox
curl -sS -X POST https://api.pixeloffice.eu/v1/mcp \
-H "Content-Type: application/json" \
-H "MCP-Protocol-Version: 2025-03-26" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "paymeter_verify",
"arguments": {
"payment_ref": "px_free_sandbox",
"price_usd": 0.002
}
}
}'Adversarial Log Hygiene, Micro-Settlement, and Blue-Green Continuity
When third-party corporate and research teams run continuous multi-step agent benchmarks against an external gateway, telemetry hygiene becomes a contractual security requirement. Any unredacted exception dump can inadvertently capture upstream authorization tokens or client callback secrets.
Pre-Persistence Secret Redaction
Our transport pipeline filters every payload through isSensitiveLogKey, sanitizeLoggedString, and redactA2aLogValue before persistence. Bearer headers, sk- provider keys, session tokens, and URL query strings are masked automatically, while audit files write under symlink-protected 0o700 / 0o600 permissions.
Zero-Downtime Blue-Green Rollouts
Automated suites polling /v1/models, /api/pricing, and /api/pay/verify-crypto cannot tolerate dropped mid-benchmark connections. Production upgrades on api.pixeloffice.eu boot staged workers, pass local health verification, and atomically swap Nginx upstreams (3001 <-> 3000).
Once verification completes, orchestrators move directly from px_free_sandbox into production inference and compliance settlement: PixelRouter exposes unified OpenAI-compatible routing at https://api.pixeloffice.eu/v1 (with :flex latency-tier arbitrage), while GET /api/pay/verify-crypto and paymeter_verify validate Solana SPL-USDC transfers and HTTP x402 machine-to-machine receipts alongside EUR Stripe billing.
Already Benchmarking Our Gateway in Automated Staging?
Public discovery endpoints and px_free_sandbox are built so external engineering and procurement teams can audit protocol behavior, latency, and schema fidelity anonymously. When your orchestrators are ready to graduate from public evaluation queues to SLA-backed capacity, Pixel Office EU provisions dedicated production channels within 24 hours:
- Dedicated EU throughput envelopes & Pro (EUR 49/mo) / Enterprise (EUR 299/mo+) quotas
- Zero-Data-Retention (ZDR) routing & EU GDPR DPA compliance packages
- Mutually authenticated A2A recontact channels & custom partner directory listing
- Unified settlement via Stripe EUR invoicing, Solana SPL-USDC, or HTTP x402