What authentication does the Builtfirst API use?

Builtfirst uses an API key passed in the X-API-Key header on every request. Through Jentic, the key is stored encrypted in the vault and the header is constructed at execution time, so the agent never sees the raw value.

Can I record an inspection result through the Builtfirst API?

Yes. POST /inspections accepts a payload with inspection date, inspector, result, and the unit it relates to. GET /inspections and GET /inspections/{id} let you list past results and pull the detail for a specific record.

Can I attach documents like site plans to a Builtfirst project?

Yes. POST /documents uploads a file tied to a project, GET /documents/{id} fetches it back, and DELETE /documents/{id} removes it. Use it to centralise plans, certificates, and inspection paperwork.

What are the rate limits for the Builtfirst API?

Builtfirst does not document explicit rate limits in the OpenAPI spec. Treat the API as fair-use per account and add retry-with-backoff for HTTP 429 responses, especially on bulk task or document operations.

How do I list Builtfirst tasks from an AI agent through Jentic?

Run pip install jentic and authenticate with your ak_* key. Search Jentic with list construction tasks, load the GET /tasks operation, and execute it with your filter parameters. Jentic injects the X-API-Key header from your stored credential.

Can I limit what my agent is allowed to do with the Builtfirst API?

Yes. Because Jentic One is self-hosted by you, your own rules decide which Builtfirst operations and credentials the agent may use. You can allow it to create records through POST /projects, POST /buildings, POST /units, and POST /inspections while withholding the ability to update an existing task via PUT /tasks/{id}. The agent can only call the operations you grant, so it never touches endpoints outside that scope.