Neva

Neva is a self-described "builder" agent: an A2A 0.3.0 agent at neva.dt-agent.co.uk that advertises one skill, Build Together, offering to co-build APIs, agent services, MVPs and integrations with other agents. Its operator publishes no website, documentation, pricing or contact - the whole public surface is an anonymous JSON-RPC endpoint at the host root and the agent card served at /.well-known/agent-card.json (and the legacy /.well-known/agent.json), listed on a2aregistry.org since 2026-03-22. As of 2026-09-19 the endpoint answers and validates requests, but a well-formed message/send fails with a wrapped upstream 401 because the agent's own model-provider API key is invalid - a condition the registry's maintainers record on the same day.

Neva is listed with 1 API on the APIs.io network. Tagged areas include A2A, AI Agents, Agent Services, Software Development, and JSON-RPC.

Neva’s developer surface includes authentication and 10 more developer resources.

🌐 Visit website 📡 Source on GitHub

10.1/100 minimal ▬ flat Agent 14/100 agent aware Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0

1 API

A2A AI AgentsAgent ServicesSoftware Development JSON-RPC Prototyping Integration Collaboration

Kin Score

Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0

Composite quality — 10.1/100 · minimal

Contract Quality 0.0 / 21

Developer Ergonomics 2.0 / 17

Access Clarity 0.0 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 4.6 / 9

Regulatory Posture 2.5 / 15

Agent readiness — 14/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 8 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/dt-agent-co-uk: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

JSON RPC

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

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. mess...

Pricing Plans 1

Published pricing tiers and plan structures.

Dt Agent Co Uk Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Dt Agent Co Uk Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Dt Agent Co Uk Authentication

none · 1 scheme

SECURITY

Dt Agent Co Uk Domain Security

TLSv1.3

SECURITY

Resources

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Conformance

Lifecycle

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 1

Pricing, plans, and the legal terms of use

Plans

Plans

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

AgentCard

AgentCard

Source (apis.yml)

aid: dt-agent-co-uk
name: Neva
description: 'Neva is a self-described "builder" agent: an A2A 0.3.0 agent at neva.dt-agent.co.uk that advertises one skill,
  Build Together, offering to co-build APIs, agent services, MVPs and integrations with other agents. Its operator publishes
  no website, documentation, pricing or contact - the whole public surface is an anonymous JSON-RPC endpoint at the host root
  and the agent card served at /.well-known/agent-card.json (and the legacy /.well-known/agent.json), listed on a2aregistry.org
  since 2026-03-22. As of 2026-09-19 the endpoint answers and validates requests, but a well-formed message/send fails with
  a wrapped upstream 401 because the agent''s own model-provider API key is invalid - a condition the registry''s maintainers
  record on the same day.'
url: https://raw.githubusercontent.com/api-evangelist/dt-agent-co-uk/refs/heads/main/apis.yml
x-type: company
x-source: harvest:a2a-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-09-19 (local-v3; was a2a-registry harvest stub)
specificationVersion: '0.20'
created: '2026-09-19'
modified: '2026-09-19'
tags:
- A2A
- AI Agents
- Agent Services
- Software Development
- JSON-RPC
- Prototyping
- Integration
- Collaboration
apis:
- 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).
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://neva.dt-agent.co.uk/
  name: Provider URL declared in the agent card (provider.url); answers 405 to GET - it is the JSON-RPC endpoint, and no HTML
    site exists
- type: AgentCard
  url: a2a/dt-agent-co-uk-a2a.yml
  name: A2A Agent Card
- type: LLMsTxt
  url: llms/dt-agent-co-uk-llms.txt
- 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: Plans
  url: plans/dt-agent-co-uk-plans-pricing.yml
- type: Conformance
  url: conformance/dt-agent-co-uk-conformance.yml
- type: Lifecycle
  url: lifecycle/dt-agent-co-uk-lifecycle.yml
- type: DomainSecurity
  url: security/dt-agent-co-uk-domain-security.yml
x-website:
  replaced: https://dt-agent.co.uk/
  status_of_replaced: 404
  current: https://neva.dt-agent.co.uk/
  status_of_current: 405
  basis: provider.url declared in the agent card; also the a2aregistry.org listing url
  note: 'The harvest stub pointed Website at https://dt-agent.co.uk/, which returns a text/plain 404 for its root and every
    other path (confirmed 2026-09-19); www.dt-agent.co.uk has no DNS record. The pointer was replaced with the URL the provider
    declares for itself in its own agent card (provider.url), the same URL a2aregistry.org lists. It is the agent endpoint
    rather than a web page - GET answers 405 Allow: POST - but it is the provider''s own, self-declared address and the only
    live host it operates. Not constructed from the slug.'
x-enrichment:
  date: '2026-09-19'
  status: enriched
  artifacts_added: 13
  pass: local-v3
x-a2a:
  verified: true
  probed: '2026-09-26'
  url: https://neva.dt-agent.co.uk/.well-known/agent-card.json
  grade: conformant
  protocol_version: 0.3.0
  control: 404

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/dt-agent-co-uk"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/dt-agent-co-uk/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/dt-agent-co-uk/evidence"

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.

GitHub Google LinkedIn

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