jupiter-vrfd

Automate Jupiter token verification by running eligibility checks, crafting unsigned 1000 JUP payment transactions, and submitting signed execute requests via the public API. This Skill handles the entire VRFD flow, including optional metadata updates.

The Jupiter VRFD express verification process checks token eligibility, crafts a 1000 JUP payment transaction, and executes the signed transaction to create or update verification records. It requires proper tokenId normalization and an x-api-key.

Submit token metadata updates during Jupiter verification by passing an eligible token mint through the craft-txn and execute endpoints. Optional metadata updates are included in the same paid flow after signing the transaction.

Yes, you need a valid x-api-key to access the public Jupiter API for crafting unsigned verification transactions. The API requires correct handling of the check-eligibility, craft-txn, and execute endpoints.

Yes, you can check token eligibility before paying by calling the GET /tokens/v2/verify/express/check-eligibility endpoint. This determines if a token can verify or submit metadata before you craft the 1000 JUP payment transaction.

The execute request fails if the crafted 1000 JUP payment transaction is not properly signed or if tokenId normalization is incorrect. Ensure your wallet signs the unsigned transaction from craft-txn before submitting it to the execute endpoint.