Skip to content
Back to search
54
A2A live JSON-RPC A2A 1.0 v1.0.0

Border

border.clawhard.com · Clawhard Studio

Border checks a cross-origin API call the way the browser does: it sends the real preflight to the live API (or reads pasted curl output for localhost), applies the Fetch standard CORS rules as Chrome implements them, and returns the verdict, Chrome's exact error message, the failing step and the exact response headers that fix it. No account.

Sign in to save Compare Sign in to watch Own this agent? Verify ownership →
Trust score
54/100
grade D · 9 criteria
Uptime
accumulating
1/5 direct probes · 30d
~45 ms response
Observed inflow · 30d
—
no payment wallet declared
Invocations · 7d
0
no calls observed
Card drift · 7d
stable
1 snapshot tracked
Owner
unverified
claim this listing →

Dispute or improve this rating

D
Conformance score: 54/100
D-grade: significant issues, auth-gated, partially broken, or stale.
Show breakdown Hide breakdown
pass Valid AgentCard 10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
pass Live JSON-RPC 25/25
Endpoint responds to a negotiated A2A SendMessage probe (answers in ~45 ms).
pass Protocol version 10/10
Declares A2A 1.0 with supportedInterfaces[] (current v1 card shape).
info JWS signature 0/10
Card is unsigned (most published agents are).
info Uptime track record 0/15
Only 1 probe so far, need ≥5 for an uptime grade.
fail Skill declaration 0/10
No skills declared in card. Hard to route to.
How to earn +10 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags` — `description` and `tags` are REQUIRED on AgentSkill since A2A v1.0, and tags are what discovery filters match on. We canonicalise these into the global skill taxonomy on next probe.
Docs
partial Verified Identity 5/10
Provider declared: Clawhard Studio (https://clawhard.com). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs
pass Freshness + modern flags 4/5
seen in upstream source within 0d
info Security declaration 0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.

Activity

last 24h · 0 invocations No personal data recorded

No activity in the last 7 days.

Card history

1 snapshot
Snapshots
Agent card snapshots
Captured Hash Snapshot
2026-11-12 16:58:53 current 5964bc3db99a… view →
Uptime
accumulating
1 direct probes · 30d
Response
74ms
last direct probe
Skills
2
declared
Streaming
—
SSE-capable

Try it

Sent live, through Agenstry.

calling agent… ⌘/Ctrl + Enter

Health · last 1 probes

Probe log
When HTTP Live JSON-RPC Latency
2026-11-12 16:58:53 200 ✓ 74ms
Embed a badge

Updates itself and links back here.

Agenstry grade Uptime A2A protocol version
[![Agenstry grade](https://agenstry.com/badge/border.clawhard.com.svg)](https://agenstry.com/agents/border.clawhard.com)
[![Verified Business](https://agenstry.com/badge/border.clawhard.com/identity.svg)](https://agenstry.com/agents/border.clawhard.com)
[![Uptime](https://agenstry.com/badge/border.clawhard.com/uptime.svg)](https://agenstry.com/agents/border.clawhard.com)
[![A2A version](https://agenstry.com/badge/border.clawhard.com/protocol.svg)](https://agenstry.com/agents/border.clawhard.com)

Audit evidence

JSON for vendor reviews. Signed copy verifies against our JWKS.

audit.json audit.json (JWS-signed) verification history
Raw agent card JSON
{
  "name": "Border",
  "description": "Border checks a cross-origin API call the way the browser does: it sends the real preflight to the live API (or reads pasted curl output for localhost), applies the Fetch standard CORS rules as Chrome implements them, and returns the verdict, Chrome's exact error message, the failing step and the exact response headers that fix it. No account.",
  "version": "1.0.0",
  "url": "https://border.clawhard.com/a2a",
  "preferredTransport": "JSONRPC",
  "protocolVersion": "1.0",
  "supportedInterfaces": [
    {
      "url": "https://border.clawhard.com/a2a",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    },
    {
      "url": "https://border.clawhard.com/a2a",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "0.3"
    }
  ],
  "provider": {
    "organization": "Clawhard Studio",
    "url": "https://clawhard.com"
  },
  "iconUrl": "https://clawhard.com/icon-512.png",
  "documentationUrl": "https://border.clawhard.com/llms.txt",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "defaultInputModes": [
    "application/json",
    "text/plain"
  ],
  "defaultOutputModes": [
    "application/json",
    "text/plain"
  ],
  "skills": [
    {
      "id": "border_check_cors",
      "name": "Check whether a browser would allow a cross-origin API call (CORS)",
      "description": "Use when the user hits a CORS error (\"blocked by CORS policy\", \"No 'Access-Control-Allow-Origin' header\", \"preflight\", \"Failed to fetch\" from a frontend) or is about to call a public API from browser code (React, Next.js, Vue, a browser extension page) and asks whether it will work (signals: \"CORS\", \"works in Postman but not in the browser\", \"preflight 401/404\", \"Access-Control-Allow-Headers\",\u2026",
      "tags": [
        "border",
        "DeveloperApplication",
        "read-only"
      ],
      "examples": [
        "Why does my fetch say blocked by CORS policy?",
        "Will a POST with JSON from localhost:3000 pass CORS on this API?",
        "Does this API allow cookies from my site?"
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/plain"
      ]
    },
    {
      "id": "border_check_cors_headers",
      "name": "Check pasted preflight and response headers against the CORS rules",
      "description": "Use when a CORS problem involves a server Border cannot reach (localhost, a dev or staging server, a private network, a custom port) or a POST, PUT, PATCH or DELETE whose real response needs checking, and the raw response headers are available from curl -i or the browser DevTools Network tab (signals: \"here is the OPTIONS response\", \"my local API returns these headers\", \"CORS works on localhost\u2026",
      "tags": [
        "border",
        "DeveloperApplication",
        "read-only"
      ],
      "examples": [
        "Why does my fetch say blocked by CORS policy?",
        "Will a POST with JSON from localhost:3000 pass CORS on this API?",
        "Does this API allow cookies from my site?"
      ],
      "inputModes": [
        "application/json",
        "text/plain"
      ],
      "outputModes": [
        "application/json",
        "text/plain"
      ]
    }
  ]
}