Alayacare Billable Item Management API
Browse all Swaggerhub Alayacare APIsCommunity OpenAPI document · agent-readyPaymentsPayment Processingbasic22 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically add a new billable item., retrieve list of billable items to display in billable management screen. Covers 22 operations with basic authentication.
Use for: I need to add a new billable item., I want to list of billable items to display in billable management screen, Search for modify an existing billable item, Find all deletes a single billable item
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
This end point can be used to create, edit and retrieve billable items before they can be processed in invoices. The API exposes 22 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Billable Item Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Billable Item Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.alayacare%2Fbillable-item-management-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.alayacare%2Fbillable-item-management-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Billable Item Management API.
Add a new billable item.
Retrieve list of Billable Items to display in Billable Management screen
Modify an existing billable item
Deletes a single billable item
Update multiple billable items status
Create new items for when changing payors in a COB invoice
Regenerate billable items
Use Cases
Patterns agents use Billable Item Management API for, with concrete tasks.
★ Payments Operations
Use the Billable Item Management API to perform payments operations programmatically. The API provides 22 endpoints covering core functionality including add a new billable item., retrieve list of billable items to display in billable management screen, modify an existing billable item.
Call POST /billable_item to add a new billable item.
Automated Bill_Code Management
Automate bill_code operations by combining multiple Billable Item Management API endpoints. Agents can retrieve list of billable items to display in billable management screen and then modify an existing billable item in a single workflow.
Call GET /billable_item to retrieve list of billable items to display in billable management screen, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Billable Item Management API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.
Search Jentic for 'add a new billable item.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
22 endpoints — this end point can be used to create, edit and retrieve billable items before they can be processed in invoices.
METHOD
PATH
DESCRIPTION
POST
/billable_item
Add a new billable item.
GET
/billable_item
Retrieve list of Billable Items to display in Billable Management screen
PATCH
/billable_item/{billable_item_id}
Modify an existing billable item
DELETE
/billable_item/{billable_item_id}
Deletes a single billable item
PATCH
/billable_item/set
Update multiple billable items status
POST
/billable_item/change-payor
Create new items for when changing payors in a COB invoice
PATCH
/billable_item/regenerate
Regenerate billable items
GET
/billable_item/count
Count the number of items matching the given filters
POST
/billable_item
Add a new billable item.
GET
/billable_item
Retrieve list of Billable Items to display in Billable Management screen
PATCH
/billable_item/{billable_item_id}
Modify an existing billable item
DELETE
/billable_item/{billable_item_id}
Deletes a single billable item
PATCH
/billable_item/set
Update multiple billable items status
POST
/billable_item/change-payor
Create new items for when changing payors in a COB invoice
PATCH
/billable_item/regenerate
Regenerate billable items
GET
/billable_item/count
Count the number of items matching the given filters
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Billable Item Management API by hand means setting up its HTTP basic auth over https, resolving the right tenant host from the templated URL, and calling billable item create, patch, and delete operations yourself. Through Jentic you install once, import the Billable Item Management API from the API Directory, store the basic credential once, and your agent calls it.
Permission scoping
The Billable Item Management API puts the billable item id in the URL path (/billable_item/{billable_item_id}), so a rule can pin your agent to one billable item: it can read that item and nothing else. You choose the operations it may call, so ones that change or remove data like patch, delete, or change payor are not included unless you add them.
Credential isolation
Your Billable Item Management API basic credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a new billable item' or 'count billable items', and Jentic returns the matching Billable Item Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Billable Item Management API through Jentic.
What authentication does the Billable Item Management API use?
The Billable Item Management API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I add a new billable item. with the Billable Item Management API?
Yes. Use the POST /billable_item endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Billable Item Management API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I add a new billable item. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add a new billable item.'. Jentic returns the matching Billable Item Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Billable Item Management API have?
The Billable Item Management API exposes 22 endpoints covering bill_code, bill_code_modifier, bill_rate operations.
Can I limit what my agent is allowed to do with the Billable Item Management API?
Yes. Because you run Jentic One yourself, your own rules decide which billable item operations and credentials the agent may use. Since the billable item id sits in the URL path (/billable_item/{billable_item_id}), you can pin the agent to a single item so it reads that item and nothing else. You choose the operations it may call, so data-changing ones like PATCH, DELETE, and the change-payor call are excluded unless you add them.
GET STARTED