canonical: https://jentic.com/apis/swaggerhub.lic/animal-identity-service-boundary # Lic Animal Identity Service Boundary swaggerhub.lic/animal-identity-service-boundary version v2. The API exposes 8 endpoints. ## For AI agents Programmatically gets animals details using their animal keys. if a date range is supplied, the , gets the latest note lodged against an animal, that the caller has permission to. Covers 8 operations. ## Scope Does not handle payments, communications, or crm - use for identity and authentication only. ## Capabilities - Gets animals details using their animal keys. If a date range is supplied, the - Creates a new note against the subject animal where the user has permission to d - Idempotently updates an existing note for a subject animal - Deletes a note on an existing animal - Monitor Animal Identity Service Boundary operational status and events ## Use cases ### Identity and Authentication Operations Use the Animal Identity Service Boundary to perform identity auth operations programmatically. The API provides 8 endpoints covering core functionality including gets animals details using their animal keys. if a date range is supplied, the , gets the latest note lodged against an animal, that the caller has permission to, creates a new note against the subject animal where the user has permission to d. Example prompt: Call POST /v2/animals/{startDate}/{endDate} to gets animals details using their animal keys. if a date range is supplied, the ### Automated Animals Management Automate animals operations by combining multiple Animal Identity Service Boundary endpoints. Agents can gets the latest note lodged against an animal, that the caller has permission to and then creates a new note against the subject animal where the user has permission to d in a single workflow. Example prompt: Call GET /v2/animals/{animalKey}/notes/latest to gets the latest note lodged against an animal, that the caller has permission to, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Animal Identity Service Boundary 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 none tokens manually. Example prompt: Search Jentic for 'gets animals details using their animal keys. if a date range is supplied, the ', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /v2/animals/{startDate}/{endDate} | Gets animals details using their animal keys. If a date range is supplied, the | | GET | /v2/animals/{animalKey}/notes/latest | Gets the latest note lodged against an animal, that the caller has permission to | | POST | /v2/animals/{animalKey}/notes | Creates a new note against the subject animal where the user has permission to d | | GET | /v2/animals/{animalKey}/notes | Gets all notes lodged against an animal | | PUT | /v2/animals/{animalKey}/notes/{noteIdentifier} | Idempotently updates an existing note for a subject animal | | DELETE | /v2/animals/{animalKey}/notes/{noteIdentifier} | Deletes a note on an existing animal | | GET | /v2/herds/{animalGroupBpNumber}/notes | Gets all notes for each animal in a herd | | GET | /v2/notes/categories | Gets all note categories | ## Key resources - **Animals** — Operations for animals - **Herds** — Operations for herds - **Notes** — Operations for notes ## Why Jentic - **Setup:** Wiring the Animal Identity Service Boundary by hand means mapping its animal-note routes, coding each GET, POST, PUT, and DELETE, and handling retries yourself. Through Jentic you install once, import the Animal Identity Service Boundary from the API Directory, store any host details once, and your agent calls it. - **Permission scoping:** This API puts the animal key in the URL path (/v2/animals/{animalKey}/notes/...), so a rule can pin your agent to the notes of one animal: it can read and add notes there and nothing else. You choose the operations it may call, so destructive ones like note update or note deletion are not included unless you add them. - **Credential handling:** Any access details for the Animal Identity Service Boundary are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get an animal by its key' or 'add a note to an animal', and Jentic returns the matching Animal Identity Service Boundary operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Auth0** — Alternative identity auth API - **Okta** — Alternative identity auth API ## FAQ ### What authentication does the Animal Identity Service Boundary use? The Animal Identity Service Boundary uses no authentication. 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 gets animals details using their animal keys. if a date range is supplied, the with the Animal Identity Service Boundary? Yes. Use the POST /v2/animals/{startDate}/{endDate} endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Animal Identity Service Boundary? 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 gets animals details using their animal keys. if a date range is supplied, the through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets animals details using their animal keys. if a date range is supplied, the '. Jentic returns the matching Animal Identity Service Boundary operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Animal Identity Service Boundary have? The Animal Identity Service Boundary exposes 8 endpoints covering animals, herds, notes operations. ### Can I limit what my agent is allowed to do with the Animal Identity Service Boundary? Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. Because this API puts the animal key in the URL path, such as /v2/animals/{animalKey}/notes, you can pin the agent to a single animal and let it only read or add notes there. You choose the operations it may call, so destructive ones like updating a note (PUT) or deleting a note (DELETE) are excluded unless you explicitly grant them.