# LogicNodes Aptos Asset Resolve

> LogicNodes Aptos Asset Resolve is a paid API for AI agents from logicnodes.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-28).

Resolves an Aptos blockchain asset by name or identifier query, returning canonical asset details on mainnet or testnet.

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/aptos_asset_resolve?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-aptos-asset-resolve-c9309f14
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IxFR_8eQfZKcLnjZ4eXK2

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 logicnodes-aptos-asset-resolve-c9309f14 -d '<json body>'
```

Example prompt: Can you resolve the Aptos asset named 'USDC' on Aptos mainnet and give me its canonical on-chain address and metadata?

## When to prefer this

Use this endpoint when you need to resolve a human-readable Aptos asset name or ticker to its canonical on-chain address or metadata. Prefer it over general blockchain explorers when you need a programmatic, structured response suitable for agent workflows, and when you need to distinguish between Aptos mainnet and testnet assets.

## Known failure modes

- Asset not found for the given query string — returns ok:false or empty result
- Invalid CAIP-2 chain ID format — returns validation error
- Ambiguous query matching multiple assets — may return list or top match
- Network connectivity issues to Aptos node — returns error response
- Case sensitivity mismatch causing no results when asset exists under different casing

## How this service works

Exact answers for AI agents: 40+ tools for EVM chains and Aptos, gas on 14 chains, never a guess. Free tier; pay per call in USDC (x402) on 13 networks.

## Output

A JSON object with ok:true and the tool name, plus resolved asset details including the canonical on-chain address, asset type, and metadata for the matched Aptos asset (mainnet or testnet as requested).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string",
   "description": "Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)"
  },
  "query": {
   "type": "string"
  },
  "caseSensitive": {
   "type": "boolean"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "aptos_asset_resolve"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-aptos-asset-resolve-c9309f14/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from logicnodes.io](https://www.zero.xyz/host/logicnodes.io/llms.txt)