Interop
A2A mapping
Export an internal Agent Card as an official A2A v1.0 profile, or import an external A2A card as a registry stub. Platform-native fields stay internal. This is a mapping boundary — not an A2A runtime. External discovery still expects /.well-known/agent-card.json.
Export
Internal → A2A. Primary endpoint prefers protocol a2a, then http / grpc by priority.
agent:research.gpuaas.v1@1.0.0 · JSONRPC · a2a-mapper.v1
{
"name": "gpuaas-research",
"description": "Early vertical test. Conceptual GPU-as-a-service research only — allocation, bid ranking, and scheduling notes. No live quotes, no booking, no settlement.",
"version": "1.0.0",
"url": "https://agents.example/gpuaas-research",
"supportedInterfaces": [
{
"url": "https://agents.example/gpuaas-research",
"protocolBinding": "JSONRPC",
"protocolVersion": "1.0"
}
],
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false
},
"defaultInputModes": [
"text/plain",
"application/json"
],
"defaultOutputModes": [
"text/plain",
"application/json"
],
"skills": [
{
"id": "gpuaas",
"name": "GPUaaS literature review",
"description": "Retrieve conceptual notes on GPU-as-a-service allocation, bid ranking, and multi-tenant scheduling. Refuses live quotes and booking.",
"tags": [
"gpuaas",
"compute",
"pricing",
"allocation",
"research",
"literature-review"
]
}
],
"provider": {
"organization": "research"
}
}Import
A2A → internal stub. Missing id is synthesized from source URL + name. Richer local fields are kept unless you overwrite.
Mapper log
Direction, agent id + version, source URL, mapper a2a-mapper.v1.
| When | Dir | Type | Agent | Schema | Source |
|---|---|---|---|---|---|
| No export or import recorded yet. | |||||