digiantnz
digiantnz is a Christchurch, New Zealand operator that runs a2a-browser, a self-hosted, account-less, pay-per-query web retrieval agent published as an A2A 0.3 agent card at a2a-browser.digiant.nz. The agent exposes two skills over a JSON-RPC 2.0 endpoint — Web Search (SERP query with LLM synthesis and entity extraction) and Page Fetch (Playwright-rendered fetch with a 50k-character cap) — identifies callers by an Ed25519 public key instead of a signup, runs a free FIFO tier at 10 requests/hour, and quotes a paid tier live in satoshis (10 per search, 20 per fetch, 1,000 minimum, Lightning) that the card still marks alpha. No OpenAPI, documentation site, MCP server or SDK is published; the registrable domain digiant.nz redirects to a Web3 name (digiant.crypto) that public DNS does not resolve.
digiantnz is listed with 1 API on the APIs.io network. Tagged areas include Company, A2A, Agents, Web Search, and Web Scraping.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| x402 Micropayments & Agentic Pay-per-Call | undeclared | - | - | 1 |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
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.
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
a2a-browser A2A Agent
Pay-per-search web agent (version 0.1.0-alpha) served from a2a-browser.digiant.nz: a JSON-RPC 2.0 POST endpoint at the host root, an A2A agent card at the legacy /.well-known/ag...
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Digiant Nz Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
digiantnz API — frequently asked questions
Does digiantnz have an API?
Yes. APIs.io lists 1 API from digiantnz, including a2a-browser A2A Agent.
How do I authenticate with the digiantnz API?
digiantnz uses bearer-token authentication (public-key-identity · 2 schemes). The details are profiled on APIs.io as Digiant Nz Authentication.
How much does the digiantnz API cost?
APIs.io lists 2 pricing plans for digiantnz, with each plan's price, limits and inclusions under Pricing Plans on this page.
Is the digiantnz API ready for AI agents?
digiantnz has a Kin Score of 20.8 out of 100 (emerging) and an Agent Readiness score of 9.4 (agent-aware), scored by API Evangelist on 2026-11-02.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.