01
Cite a specific project conclusion
Open the project’s diligence packet, then cite the canonical project page and the linked control record supporting the specific claim.
Integration recipe guide
Choose the source surface before you copy the data.
LouisianAI exposes several public interfaces because a human citation, an embedded tracker, and an application integration need different contracts. This guide maps the job to one preferred starting point.
Diligence packets
02
Reproduce a filtered tracker slice
Use the public tracker URL, then request the matching manifest to retain filters, sort state, inclusion rules, record IDs, and an as-of timestamp.
03
Consume a machine-readable claim index
Use the claim ledger to route an answer to a canonical project, source, docket, topic, or methodology page. It is a routing file, not a substitute for primary-source review.
04
Embed a LouisianAI surface
Use supported tracker, brief, and badge embeds so readers can return to a canonical source rather than a stale copied table.
05
Integrate a feed or API
Use the documented public API, dataset, feed, and discovery files. Preserve confidence, source, as-of, and canonical-link fields in your downstream display.
Preserve the original source scope, confidence label, as-of date, and canonical link. Do not infer readership, endorsement, investment performance, regulatory approval, or commercial outcome from a discovery file, embed, or share asset.