Integration
Connect Federal Register to Billage
When something happens in Federal Register, your agent does the next thing in Billage. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Federal Register and Billage to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Federal Register and Billage
Triggers and actions 1 trigger ยท 23 actions
Trigger
New documentPolling 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 documentsSearch 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 documentsSearch public inspection documents currently scheduled for future publication. Endpoint: GET /public-inspection-documents.{format}
Action
Get agencyFetch a particular agency's details by slug. Endpoint: GET /agencies/{slug}
Action
Get documentFetch a single Federal Register document by document_number, returning its full text and metadata. Endpoint: GET /documents/{document_number}.{format}
Action
Get issueFetch a document table of contents for the print edition based on publication_date. Endpoint: GET /issues/{publication_date}.{format}
Action
Get public inspection documentFetch a single public inspection document by document_number. Endpoint: GET /public-inspection-documents/{document_number}.{format}
Action
List agenciesFetch all agency details known to the Federal Register. Endpoint: GET /agencies
Action
Add ProductCreate a new Billage product. POST /v2/products.
Action
Create AccountCreates a new account.
Action
Create ContactCreates a new contact in an account.
Action
Delete AccountDelete a Billage account by id. DELETE /v2/accounts/{account-id}.
Action
Delete ContactDelete a Billage contact by id. DELETE /v2/contacts/{id}.
Action
Delete LeadDelete a Billage lead by id. DELETE /v2/leads/{id}.
Action
Get AccountFetch a single Billage account (company/customer record) by id. GET /v2/accounts/{account-id}.
Action
Get ContactFetch a single Billage contact by id. GET /v2/contacts/{id}.
Action
Get LeadFetch a single Billage lead by id. GET /v2/leads/{id}.
Action
Get ProductFind a Billage product by id. GET /v2/products/{id}.
Action
List AccountsList/search Billage accounts by name, alias, vat, tags, etc. GET /v2/accounts.
Action
List ContactsList/search Billage contacts by criteria. GET /v2/contacts.
Action
List LeadsList Billage leads. GET /v2/leads.
Action
List ProductsList/search Billage products by alias or name. GET /v2/products.
Action
Update AccountUpdate an existing Billage account. PUT /v2/accounts.
Action
Update ContactUpdate an existing Billage contact. PUT /v2/contacts.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.