Start here. Each guide is a few steps and a working example. The API is in early access: the examples show the calls as they will work at launch.
Sign up with your work email. You get a sign-in link by email and 100 free credits for search, entries and ask.
In your portal, create an API key and choose what it may use. You see the key once; store it like a password.
Send the key in the Authorization header. Every response tells you the credits charged and the credits left.
curl https://api.lucainfra.com/v1/codex?q=backup+restore \ -H "Authorization: Bearer $KEY"
Search is 1 credit per search with results. Reading an entry buys it once; reading it again is free for a year. Ask builds an answer only from listed entries and cites them.
curl https://api.lucainfra.com/v1/codex/<slug>?format=md -H "Authorization: Bearer $KEY"
curl -X POST https://api.lucainfra.com/v1/ask -H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" -d '{"question":"How do I plan a two-site network?"}'Listing kits is free. A download is charged once, served exactly as released, with its sha256 so you can check it.
curl https://api.lucainfra.com/v1/kits -H "Authorization: Bearer $KEY" curl -LO https://api.lucainfra.com/v1/kits/<kit_id>/download -H "Authorization: Bearer $KEY" sha256sum <kit>.zip # compare with the published .sha256
Search the blueprint for the build, buy it, ask for the step you are on as a script, and keep the matching runbook open for when a step fails.
Ask for a work breakdown structure for the engagement, then a statement of work built from it; every line cites the playbooks and runbooks it rests on.
Give your AI assistant the library through Luca Nano or the API, so the code and docs it writes follow proven procedures instead of guesses.
The store opens in test mode first. Talk to us to join early access, get 100 free credits at launch, and tell us what you want in the library.