Skip to content

HLnames/use-hln-api / skills/use-hln-api

use-hln-api

Verified

Consult & 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.

FileKindSize
SKILL.mdskill md7.1 KB
references/endpoints.mdmarkdown5.1 KB
references/integration.mdmarkdown3.4 KB
references/validation-and-errors.mdmarkdown3.0 KB

references/integration.md

View on GitHub
# HyperEVM dApp Integration

Use this reference when the user is integrating HL Names into a HyperEVM dApp, wallet connection flow, or minting flow.

## Quick Workflow

1. Default read-only integration work to the production API:
   - `https://api.hlnames.xyz/`
   - Swagger docs: `https://api.hlnames.xyz/api/docs/`
2. Use the published example pair from the GitBook docs for smoke tests:
   - `testooor.hl`
   - `0xF26F5551E96aE5162509B25925fFfa7F07B2D652`
3. Pick the narrowest endpoint for the product surface:
   - Name input to address: `GET /resolve/address/:domain`
   - Wallet address to primary name or profile: `GET /resolve/profile/:address`
   - Full Data Records map, chain addresses, ownership, or expiry: `GET /records/full_record/:nameHashOrId`
   - Owner or list queries: `GET /utils/names_owner/:address`, `GET /utils/all_names`, `GET|POST /utils/all_primary_names`
4. Treat returned metadata as user-controlled profile data.
   - Common suggested/default-style keys include `Avatar`, `Twitter` or `X`, `Discord`, `Bio`, `REDIRECT`, and `CNAME`.
   - If the application needs the complete record set, follow `resolve/profile` with `records/full_record`.

## Wallet Integration

The GitBook wallet connector page documents two main paths:

- `@hlnames/rainbowkit`
  - For new projects: install `@hlnames/rainbowkit@latest` and use it where you would otherwise use `@rainbow-me/rainbowkit`.
  - For existing RainbowKit apps: install the HL Names fork of `@rainbow-me/rainbowkit@2.2.10` so current imports can stay unchanged.
  - Prefer the upstream-published GitHub install path or repository link when the goal is to follow the latest maintained HL Names integration.
- Dynamic
  - GitBook links to `https://github.com/ori-wagmi/hlnames_dynamic` for Dynamic-based integration.
  - Prefer the linked GitHub branch or repository reference when the goal is to follow the latest maintained integration example.

When the user asks for frontend wiring, start from the wallet stack they already use rather than inventing a custom resolution layer.

## REST API Notes

- The GitBook dApp integration page informs the REST API is intended for resolving names on both HyperEVM mainnet as well as HyperCore.
- For manual testing in Swagger UI, follow the current instructions on the GitBook dApp integration page.
- Keep API use read-only unless the user explicitly asks for mint-pass preparation.

## Minting Preflight

- `POST /sign_mintpass/:label` is the API preflight for third-party minting.
- The signature is valid for 1 minute, counting from the timestamp given in the response.
- Request it when the developer is ready to continue promptly into the mint transaction.
- Validate that the label is normalized and does not include the `.hl` suffix.
- The response is server-generated and intended for immediate use in the downstream mint call. If the mint is submitted after expiry, the onchain transaction should revert.

For end-to-end third-party minting examples, use the consulted public repo:
- `https://github.com/HLnames/hln_api_minting` (see README.md)
- Key example files:
  - `example/getSignedArgs.ts`
  - `example/getSignedArgs+Mint.ts`
  - `example/getSignedArgs+Mint.py`
- Treat this repo as the upstream reference point when the goal is to follow the latest maintained minting examples.

Use that repo when the user wants implementation examples for fetching signed arguments or continuing into the mint transaction flow.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall