HLnames/use-hln-api / skills/use-hln-api
use-hln-api
VerifiedConsult & operate against the Hyperliquid Names API. Use when your agent needs to resolve `.hl` names, reverse-resolve addresses, fetch HLN profiles or records, inspect owner or list queries, diagnose HLN API failures, prepare a mint-pass request, or guide HyperEVM dApp integration with HL Names.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.1 KB |
| references/endpoints.md | markdown | 5.1 KB |
| references/integration.md | markdown | 3.4 KB |
| references/validation-and-errors.md | markdown | 3.0 KB |
references/validation-and-errors.md
View on GitHub# Validation And Errors
Use this file when an HLN request fails before or after hitting the API.
## Authentication
- Send the API key in the `X-API-Key` header.
- Expect `401` with this shape when the key is missing or wrong:
```json
{ "error": "Unauthorized: Invalid API Key" }
```
- Swagger UI at `/api/docs` requires no API-key auth.
## Identifier Rules
Validate locally before calling the endpoint when possible. Swagger documents the endpoint parameter shapes, and the notes below preserve the stricter current validation guidance already captured in this skill.
| Identifier | Current API rule | Failure detail |
| --- | --- | --- |
| Domain | String ending in `.hl`, total byte length `4..32` by current validator | `Domain not valid (1-31 chars + .hl suffix)` |
| Label | String without `.hl`, byte length `1..29` by current validator | `Label not valid (1-31 chars), no .hl suffix` |
| Address | Must pass `viem` `isAddress()` | `Valid EVM address is required.` |
| NameHash | `0x` plus 64 hex chars | `NameHash must be 0x-prefixed 32-byte hex string.` |
| TokenId | Numeric string | `TokenID must be a number.` |
| NameHashOrId | Valid nameHash or numeric tokenId | `NameHash must be 0x-prefixed 32-byte hex string or a valid TokenID.` |
## Error Mapping
The API normalizes many failures into structured `error` payloads.
| Status | Meaning | Typical Shape |
| --- | --- | --- |
| `400` | Bad request body or unsupported parameter combination | `{ "error": { "message": "Bad Request.", "details": "..." } }` or route-specific `{ "error": "..." }` |
| `401` | Missing or invalid API key | `{ "error": "Unauthorized: Invalid API Key" }` |
| `404` | Name not found or endpoint-specific absence | `{ "error": { "message": "...", "status": 404 } }` |
| `405` | Unsupported method on a route that falls through to method check | `{ "error": { "message": "Method Not Allowed.", "status": 405 } }` |
| `406` | Reserved fallback | `{ "error": { "message": "Not Acceptable.", "status": 406 } }` |
| `422` | Validation failure or invalid HLN argument | `{ "error": { "message": "Unprocessable Content.", "status": 422, "details": "..." } }` |
| `500` | Internal API or upstream failure | `{ "error": { "message": "...", "status": 500 } }` or route-specific `{ "error": "..." }` |
## Observed Semantics That Matter
- `NAME_NOT_REGISTERED` maps to `404`.
- `DOMAIN_NOT_HL` and `INVALID_ARGUMENT` map to `422`.
- Contract errors may bubble up through `metaMessages`; the API surfaces the first message containing `Error:`.
- `getExpiry()` returns `0` for unregistered names rather than throwing, so do not misread an expiry of `"0"` as a valid timestamp.
## Troubleshooting Checklist
1. Confirm the environment and base URL.
2. Confirm `X-API-Key` is present and valid.
3. Confirm the identifier matches the endpoint contract.
4. Distinguish direct validation failure (`422`) from absence (`404`).
5. For `POST /utils/all_primary_names`, do not combine address-body filtering with `begin` or `end`.
6. For `POST /sign_mintpass/:label`, confirm the label has no `.hl` suffix.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |