near_account
What is this NEAR account, and who controls it? — 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. Required input: account. Priced $0.01 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"account": "<account>"
},
"name": "near_account"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | Yes | NEAR account |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | The result payload. Shape is service-specific; every field is documented in the tool description. | |
| service | No | The service id that answered. | |
| checkedAt | No | ISO-8601 timestamp of when the underlying reads were taken. |