Neva A2A Agent

Neva's agent-to-agent surface: an anonymous A2A 0.3.0 JSON-RPC endpoint at the root of neva.dt-agent.co.uk (POST only; GET returns 405) implementing the a2a-sdk method set. message/send takes a full Message with a mandatory client-supplied messageId and {"kind":"text","text":...} parts; there is no streaming, no push notifications, no queryable tasks and no authenticated extended card. One skill, build-with-us. On 2026-09-19 a well-formed message/send returned JSON-RPC -32603 wrapping an upstream HTTP 401 "API key is invalid" - the agent's own model-provider credential - so the agent validates but does not currently reply. No OpenAPI, documentation or SDK.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/neva-a2a-agent"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: dt-agent-co-uk:neva-a2a-agent
name: Neva A2A Agent
description: 'Neva''s agent-to-agent surface: an anonymous A2A 0.3.0 JSON-RPC endpoint at the root of
  neva.dt-agent.co.uk (POST only; GET returns 405) implementing the a2a-sdk method set. message/send takes
  a full Message with a mandatory client-supplied messageId and {"kind":"text","text":...} parts; there
  is no streaming, no push notifications, no queryable tasks and no authenticated extended card. One skill,
  build-with-us. On 2026-09-19 a well-formed message/send returned JSON-RPC -32603 wrapping an upstream
  HTTP 401 "API key is invalid" - the agent''s own model-provider credential - so the agent validates
  but does not currently reply. No OpenAPI, documentation or SDK.'
humanURL: https://neva.dt-agent.co.uk/.well-known/agent-card.json
tags:
- A2A
- AI Agents
- JSON-RPC
- Agent Services
properties:
- type: AgentCard
  url: a2a/dt-agent-co-uk-a2a.yml
  name: A2A Agent Card (graded, verbatim body alongside)
- type: Authentication
  url: authentication/dt-agent-co-uk-authentication.yml
- type: Conventions
  url: conventions/dt-agent-co-uk-conventions.yml
- type: ErrorCatalog
  url: errors/dt-agent-co-uk-problem-types.yml
- type: RateLimits
  url: rate-limits/dt-agent-co-uk-rate-limits.yml
- type: Conformance
  url: conformance/dt-agent-co-uk-conformance.yml
- type: Lifecycle
  url: lifecycle/dt-agent-co-uk-lifecycle.yml
overlays: []
x-humanurl-note: The provider publishes no human-readable page; the agent card is the only document that
  describes the API, so it stands in as humanURL rather than a URL that returns 404 (the apex) or 405
  (the endpoint).