Step-by-step instructions
Last updated
Last updated
Generative Inscription as a Service (IaaS) is an API set for inscribing, tracking inscribing statuses, and browsing Bitcoin inscriptions.
At Generative, we've built an infrastructure for 3rd developers to save engineering time and maintenance effort when working with Bitcoin Ordinals. In this document, we'll walk you through step-by-step how to use our APIs so you can integrate them into your applications.
Once you'd like to inscribe a file, you needs to request a payment address and then send the required BTC to the address to cover inscription fees. The Generative platform will check the balance of the address regularly and inscribe an inscription for the uploaded file to the your address when the funds land arrive.
To get the payment address, call the following api with payload:
- fileName: uploading file name
- file: file content in base64 format
- feeRate: fee rate that is used for the inscription transaction
- walletAddress: the address that you'll receive inscription
A sample response is seen below. There are three fields you should use to display on your application:
- id: inscribing request id
- segwitAddress: payment address that you need to send BTC to for covering the inscription fees
- amount: payment amount
- ordAddress: your address that will receive inscription
To check status of a particular inscribing request, call the following api. Here, {{id}} the parameter is an inscribing request id taken from step 2.
A sample of The response payload is below:
You can use `isConfirm` and `isMint` fields for checking the status of the inscribing request:
- isConfirm is true if the payment address (generated in step 2) receives sufficient funds to cover the inscription fees.
- isMint is true if the requesting inscription is successfully inscribed to the user's address.