Install Jentic One Beta

Connect the GraveHub APIs Docs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GraveHub APIs Docs, 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.

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%2Fgravehub.it%2Fgravehub" | sh

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%2Fgravehub.it%2Fgravehub" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 GraveHub APIs Docs API.

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

GET STARTED

Start building with GraveHub APIs Docs API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GraveHub APIs Docs API for, with concrete tasks.

★ 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.

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.

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.

Record a new assistance request and retrieve the matching ticket by its id

Key Endpoints

36 endpoints — 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.

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

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

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using GraveHub APIs Docs API through Jentic.

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.

Gravehub It GraveHub APIs Docs

AI ReadinessAI-Aware (B)66/100

See full scorecard

Community OpenAPI document · agent-readyCRMContact Managementbearer36 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Lets an AI agent maintain cemetery administration records, including cemeteries, sectors, burials, deceased persons, contracts, and right-holders.

Use for: Register a new cemetery in the census, Record a burial and link it to a deceased person, Retrieve a deceased person's record by id, Find all sectors in a cemetery

Not supported: Does not handle payment processing, mapping, or genealogy research. Use for cemetery administration records only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

88%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

37%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

52%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

94%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

49%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GraveHub APIs Docs to your agent

Capabilities

Start building with GraveHub APIs Docs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Gravehub It GraveHub APIs Docs

Jentic AI Readiness Score

GraveHub APIs Docs

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness