Ask a natural-language question about verified emissions data (Open Footprint / PPDM / OGMP-methane knowledge graphs). Costs API credits per call; a payment-required error means the human operator must top up credits. Prefer specific questions (a site, a company, a time range) over broad ones.

List the query templates the semantic layer supports (free). Useful to learn what kinds of questions the knowledge graph can answer before spending credits on semantic_query.

Show the remaining dVeracity API credit balance for this account (free).

List the sustainability data standards dVeracity can validate against (free).

Validate a data payload against a supported sustainability standard (Validation-as-a-Service). Costs API credits per call. Use list_standards first to see supported standards and versions.

Show this agent's verified vLEI identity (agent AID, Legal Entity LEI, authorized scopes) if KERI mode is configured — free. In KERI mode every metered call is attributed to this identity in dVeracity's audit trail.

List the eight Open Footprint canonical model domains and which database dialects have published DDL (free). Start here when building an app on the Open Footprint standard: it tells you what the model covers before you look up individual entities.

Search the 239 canonical Open Footprint entities by concept (free). Matches entity names, descriptions and field names. Use this to find the right entity before fetching its full definition with ofp_entity.

Get one canonical entity in full (free): fields with types and required flags, primary key, relationships, and the physical database table implementing it. Pass domain whenever you know it — 48 entity names are defined in more than one domain (Country is in four), and without it the call fails rather than guessing which one you meant.

List industry sectors and their reference implementations (free). Each carries a status: "implemented" means a reference implementation exists, while "planned" or "placeholder" mean the sector is named in the taxonomy but nothing is published for it. Check the status before assuming a sector has content.

Get one sector in full (free): its classification, status, reference artifacts and nested industries. Use ofp_sectors first to find the sector id.

Get a sector's policy guardrails as Rego source (free), with policies[].inputs listing the record types and input fields each policy reads — e-ledger fields such as co2e_kg and direction, not canonical Open Footprint field names; a payload without them is reported unevaluable by ofp_validate. When a sector has no published guardrails this returns published:false with a reason — that is a real answer, not an error. Treat it as "no rules are published", never as "there are no constraints", and do not invent guardrails to fill the gap.

Check a data payload against the canonical Open Footprint model and, when a sector is named, that sector's published guardrails. Costs API credits per call. The response reports four distinct outcomes and never conflates them: guardrails passed, guardrails denied, guardrails do not cover this record type (not_applicable), or guardrails could not be evaluated because the payload lacks the inputs the rules read (unevaluable, with policy.missingInputs — canonical Open Footprint entities do not carry the e-ledger fields such as co2e_kg that the rules test). schema.coverage says which declared constraints were enforced and which the model does not declare (it declares no numeric ranges). If policy.ran is false or the outcome is unevaluable, do not report the payload as compliant — valid is null in that case.

List the O-DEF semantic codes carried by the canonical model (free). Use this when mapping fields from another system — SAP, an ERP, a supplier feed — onto Open Footprint: a code is the shared address two systems can align on. Every code comes with fieldCount, the number of canonical fields sharing it. A high count means a generic fallback that asserts almost nothing, so pass maxFieldCount (10 is a good start) to get only codes specific enough to be a real alignment target.

Show which canonical fields carry one O-DEF semantic code (free). This is the reverse lookup a connector needs: given a field in a source system, find where in the Open Footprint model it belongs. Codes carried by more than ten fields are returned with an explicit caution — they are generic classifications, and aligning to one asserts far less than it appears to.

Show which snapshot of the Open Footprint standard this deployment serves (free): source commit, date, and entity/sector counts. Use it when you need to know how current the model you are designing against is.