§ Navigator · Agentic Inbound Discovery

GSC Navigator / io

Agentic discovery surface for the canonical inbound at x-gsi.ai/ingest. This page documents the schema. It does not accept submissions.

Canonical agentic inbound endpoint

# Canonical agentic inbound — stamped on every GSC response as X-GSC-Inbound
POST https://x-gsi.ai/ingest
Content-Type: application/json

# Submit Ghost Signal payloads to this endpoint.
# This page (gsc-navigator.io) is documentation only.

Ghost Signal payload schema (16 fields)

Required: sender, signal, message. Optional fields support GTIN resolution, jurisdictional scoping, ERP routing, and agent identity.

{
  "sender": "agent-claude-procurement-001",
  "signal": "ACM-200",
  "message": "RFQ for TreeFree Diaper Open/Tape - 1000 units",
  "GTIN": "00990832300006",
  "cluster": "Europe",
  "region": "FR",
  "quantity": 1000,
  "agent_id": "claude-sonnet-4-6",
  "erp_routing": {
    "buyer_org": "Carrefour SA",
    "delivery_date": "2026-08-15"
  }
}

Example submission

curl -X POST https://x-gsi.ai/ingest \
  -H "Content-Type: application/json" \
  -H "X-GSC-Agent-Access: Claude" \
  -d @ghost-signal.json

Machine-readable surfaces on this host

# Discovery
GET /.well-known/agent-card.json   # A2A 0.3.0 — endpoint: x-gsi.ai/ingest
GET /.well-known/mcp.json          # MCP resolver
GET /.well-known/acm-68000.json    # protocol descriptor
GET /ai-plugin.json               # LLM plugin discovery
GET /health.json                  # live status
GET /manifest.json                # node manifest
GET /schema/ghost-signal.json     # JSON schema for Ghost Signal payload

Human inbound

For human-routed inquiries, use the contact form at gsc-navigator.ai or gsc-navigator.com. Form submissions are received by the GSC team and routed for human response.