canonical: https://jentic.com/apis/gravehub.it/gravehub # Gravehub It GraveHub APIs Docs The GraveHub API manages cemetery administration records for the GravHub software: cemeteries, sectors, burials, deceased persons, contracts, and the right-holders tied to each plot. It records new entries, retrieves them by id or by filters such as municipality or email, and updates or removes them. It also handles user accounts, their notification settings, and support-assistance tickets, all behind a session login that issues a Bearer token. ## For AI agents Lets an AI agent maintain cemetery administration records, including cemeteries, sectors, burials, deceased persons, contracts, and right-holders. ## Scope Does not handle payment processing, mapping, or genealogy research. Use for cemetery administration records only. ## Capabilities - Register cemeteries and their sectors in the cemetery census - Record burials and retrieve deceased-person records by id - Maintain right-holder records and their contracts - Look up cemeteries, sectors, and burials by id or municipality - Handle support-assistance tickets for cemetery administration - Administer user accounts and their notification settings ## Use cases ### Agent-maintained cemetery registry An AI agent can keep a cemetery's registry current through GraveHub by registering cemeteries and sectors, recording burials, linking deceased persons, and maintaining right-holder contracts from one credential. The login-issued Bearer token gates every record operation. Connected through Jentic, the agent calls only the record and lookup operations its rule allows. Example prompt: Register a new cemetery, add one of its sectors, and record a burial linked to a deceased person ### Right-holder and contract administration Cemetery offices track who holds the rights to each plot and under which contract. GraveHub maintains right-holder records and their contracts, so an agent can look up a right-holder, update a contract, and keep the plot's entitlement accurate. This keeps the office's paperwork aligned with the burial records. Example prompt: Look up a right-holder by id and update the contract tied to their plot ### Support ticket handling Families and staff raise assistance requests about plots, records, and paperwork. GraveHub records support-assistance tickets and retrieves them by id, so an agent can triage incoming requests and update their status. User notification settings let the office control who is alerted. Example prompt: Record a new assistance request and retrieve the matching ticket by its id ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/jwt/auth/login` | Log the user into the system | | GET | `/cimiteri/api/method/get` | Retrieve cemeteries by id or municipality | | POST | `/cimiteri/api/method/post` | Register a cemetery | | GET | `/sepoltura/api/method/get` | Retrieve a burial by id | | POST | `/sepoltura/api/method/post` | Record a burial | | GET | `/defunti/api/method/get` | Retrieve deceased persons by id | | POST | `/assistenza/api/method/post` | Record a support-assistance request | ## Key resources - **Cemeteries and sectors** — Register and retrieve cemeteries and their sectors - **Burials and deceased** — Record burials and look up deceased-person records - **Right-holders and contracts** — Maintain right-holder records and the contracts tied to plots - **Assistance** — Record and retrieve support-assistance tickets - **Users** — Administer user accounts and notification settings ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 72 / 100 - Developer Experience & Jentic Compatibility: 78 / 100 - AI-Readiness & Agent Experience: 49 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 60 / 100 - **View full report:** https://jentic.com/apis/gravehub.it/gravehub/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring GraveHub by hand means running its session login, carrying the Bearer JWT on every record call, and mapping the Italian resource paths yourself. Through Jentic you install once, import GraveHub from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** GraveHub carries record ids and filters in the path and body, so a rule bounds which operations your agent may call rather than which cemetery. You choose the operations it may call, so the delete operations are not included unless you add them. - **Credential handling:** Your GraveHub token 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. - **Discovery method:** Agents search Jentic by intent such as 'record a burial' or 'look up a cemetery', and Jentic returns the matching GraveHub operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Axonaut API** — General SMB management and CRM versus GraveHub's cemetery-specific records. - **Novi AMS API** — Association membership records versus GraveHub's cemetery registry. - **SwiftFox External API Gateway** — A contact CRM to pair with GraveHub for the people behind the records. ## FAQ ### What authentication does the GraveHub API use? GraveHub authenticates with a Bearer JWT token obtained from its login operation and sent in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context. ### Can I record burials and look up deceased persons with the GraveHub API? Yes. The burial operations record a burial and retrieve it by id, and the deceased-person operations retrieve records by id. You can also register cemeteries and sectors, maintain right-holder contracts, and handle support-assistance tickets. ### What are the rate limits for the GraveHub API? The OpenAPI spec does not specify rate limits for the record and lookup operations. Check https://gravehub.it for current limits. ### How do I record a burial with the GraveHub API through Jentic? Search Jentic for 'record a burial' and it returns the GraveHub burial operation with its input schema, so your agent fills the body and calls it after logging in. Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import GraveHub from the API Directory, and store your credential once. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with GraveHub? Yes. Write a rule that allows only the lookup operations that read cemeteries, burials, and right-holders, so the agent can research records but cannot delete or update them, and every call it makes is logged. ### Is there a GraveHub MCP server? You don't need an MCP server to connect your agent to GraveHub. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers and calls the operations it needs on demand.