# NEAR Account Check

> NEAR Account Check is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Inspects a NEAR account to reveal its type, NEAR balance breakdown, contract/token status, and full-access/function-call key authorizations — live from the NEAR RPC.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/near-account?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/near-account-check-be54beb5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TdQ6bIrY3rwfIVAvaGDQf

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability near-account-check-be54beb5
```

Example prompt: Before I send NEAR to alice.near, can you check if that account actually exists, what kind of account it is, how much NEAR it holds, and who has signing authority over it?

## When to prefer this

Use this endpoint when you need a comprehensive, single-call pre-flight check on a NEAR account before executing a payment, establishing trust, or auditing key authority. Prefer it over manual RPC calls when you need balance breakdown (available vs staked vs storage-locked), contract detection, and key enumeration in one response without assembling multiple NEAR RPC queries yourself.

## Known failure modes

- Account does not exist on NEAR mainnet — returns not-found flag
- Invalid account ID format — query rejected
- NEAR RPC node unavailable — timeout or 503 error
- Rate limit exceeded — 429 response

## How this service works

Before an agent pays or trusts a NEAR account: does it exist, what kind is it (named, implicit, 0x), how much NEAR it holds (available, staked, locked for storage), whether it is a contract or a NEP-141 token, and who controls it — full-access keys that can do anything, and function-call keys limited to one contract. Flags a wallet held by one key, a contract replaceable by key, and an account no one can sign for. Live from the NEAR RPC.

## Output

Returns the account's existence status, account type (named, implicit, or 0x-style), available/staked/storage-locked NEAR balances, whether it is a deployed contract, whether it implements NEP-141, a list of full-access keys and function-call keys (with their permitted contracts), and security flags such as single-key wallet, key-replaceable contract, or keyless/locked account.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "account"
     ],
     "properties": {
      "account": {
       "type": "string",
       "description": "NEAR account"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/near-account-check-be54beb5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)