Connect CryptAPI to Federal Register

Both apps 16CryptAPI 8Federal Register 8

• Trigger
  Payment received (instant)

  Fires when a payment address created via Create payment address receives funds; CryptAPI calls the callback URL supplied at creation time with the payment details.

• Action
  Convert price

  Convert a value between a fiat currency and a cryptocurrency, or between two cryptocurrencies, for a given ticker.

• Action
  Create payment address

  Generate a new cryptocurrency payment address for a given ticker (e.g. btc, eth, trc20/usdt) that a customer can send funds to, with a callback URL for payment notifications.

• Action
  Estimate blockchain fees

  Estimate the blockchain network fee to forward a transaction to a wallet address, for a given cryptocurrency ticker.

• Action
  Generate payment QR code

  Generate a base64-encoded QR code image for a payment address, for a given cryptocurrency ticker.

• Action
  Get payment address logs

  Get the callback/payment activity log for a previously created payment address, for a given ticker.

• Action
  Get ticker info

  Get details (minimum transaction amount, fees, current price) for a specific cryptocurrency ticker.

• Action
  List supported cryptocurrencies

  List all cryptocurrencies and blockchains supported by CryptAPI, with logos, minimum transaction amounts, and fee tiers.

• Trigger
  New document

  Polling trigger that fires when a new Federal Register document is published, using GET /documents.{format} sorted by publication_date descending as the dedup source for regulatory monitoring.

• Action
  Find documents

  Search all Federal Register documents published since 1994 by term, agency, document type, publication/effective date, and docket number. Endpoint: GET /documents.{format}

• Action
  Find public inspection documents

  Search public inspection documents currently scheduled for future publication. Endpoint: GET /public-inspection-documents.{format}

• Action
  Get agency

  Fetch a particular agency's details by slug. Endpoint: GET /agencies/{slug}

• Action
  Get document

  Fetch a single Federal Register document by document_number, returning its full text and metadata. Endpoint: GET /documents/{document_number}.{format}

• Action
  Get issue

  Fetch a document table of contents for the print edition based on publication_date. Endpoint: GET /issues/{publication_date}.{format}

• Action
  Get public inspection document

  Fetch a single public inspection document by document_number. Endpoint: GET /public-inspection-documents/{document_number}.{format}

• Action
  List agencies

  Fetch all agency details known to the Federal Register. Endpoint: GET /agencies

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.