API Terms

Effective 13 September 2026Last updated 13 September 2026api-terms-2026-09-13

These terms cover the fixRAgent triage API: POST /api/triage, the outcome callback at /api/outcome, and anything else described at /docs. They sit on top of the Terms of Service and the Privacy Policy, which also apply to you and to everything you send through the API. If these API Terms and the Terms of Service disagree about the API, these win.

By sending a request you agree to these terms. If you send it on behalf of a company, you agree for the company and confirm you are allowed to.

1. Keys

• A key is sent in the x-triage-key header. We issue keys and we own them. A key is for one party; do not share it, publish it, or put it in code that ships to a browser.
• There is no self-service key today. To ask for one, write to legal@fixragent.com or use the feedback form in the app, and say what you are building; the documentation at /docs describes the header, the limits and the answer.
• We may revoke, replace or re-scope any key at any time, with or without notice.
• When no key is configured on our side, the door is open and every answer says so — in the warnings field and in an X-Triage-Warning header. An open door is a state we can close at any moment. Do not build on it.

2. Limits

Three limits stand in front of the door, in this order, and each one tells you when to come back:

• Per address. 20 requests per IP address per hour. Over that you get 429 rate_limited with Retry-After.
• Per key. The demo key allows 60 requests per UTC day. Over that you get 429 demo_key_quota.
• Daily spend fuse. When the day's computed model spend reaches our limit you get 503 budget_exhausted with Retry-After set to the seconds until 00:00 UTC. The figure behind the fuse is computed from token counts and a price table, not read from a bill, and the response says so.

A photo must be a JPEG, PNG or WebP of 3 MB or less. We may change any limit, and add new ones, at any time. Working around a limit — rotating addresses, sharing keys, retrying past a Retry-After — is a breach of these terms.

3. What you may do with the answer

• You may use the JSON we return inside your own product or workflow, and show it to your users.
• If you show a card to a person, keep the urgency word and the hazard text with it. Do not strip the tier, raise or lower it, or present the answer as an inspection, a licensed opinion or a certification. The Terms of Service section on danger applies to everyone who sees the output through you.
• You may not use the API, or the answers it returns, to build a dataset for training or tuning a model that competes with the engine, or to resell the raw output as a service of your own.
• You may say your product uses fixRAgent. You may not say we endorse or certify your product.

4. The photos you send

• You are responsible for having the right to send each photo. Where a photo shows a resident's home, you obtain whatever permission the law where they live requires, and you tell them, in your own privacy notice, what happens to it.
• What happens to it is in our Privacy Policy: the photo's metadata is stripped on our server before anything else; a photo that cannot be cleaned is refused; the stripped photo is sent to the model provider, which keeps it for its stated period; we keep no copy of the photo's bytes on this endpoint — only its hash, the answer, and the versions that produced it.
• For the read itself we act on your instructions. For the stored answer, the outcome records and everything de-identified, we act on our own account under the licence in section 5.

5. Licence and data rights

Section 6 of the Terms of Service — the licence over your content, de-identified and aggregate data, what survives deletion and the consent record — applies to everything sent through the API: photos, text, and every outcome you post to the callback. The diagnosis_id we return is the key that joins an outcome to its read, and outcomes you post become part of the same record. If your organisation has a signed written agreement with ARLogic, that agreement changes this section only where it says so expressly.

6. What we do not promise

• We do not promise that the API will be available at any particular time, will answer within any particular time, or will keep working in any particular way. There is no service-level commitment of any kind.
• We may throttle, suspend, change or withdraw the API, or any key, at any time.
• The shape of the answer is documented at /docs and carries a contract version. We try to add fields rather than change them, and to note breaking changes in the docs before they land, but we do not promise either.
• An answer can be wrong. The engine reads one photo. Everything the Terms of Service says about that applies to answers you receive through the API.

7. Fees

The demo key is free. Any paid arrangement — volume, a dedicated key, support, a written agreement — is a separate written agreement between you and ARLogic. Nothing here creates one.

8. Warranty, liability and your responsibility to others

Sections 9, 10 and 11 of the Terms of Service apply to the API in full: no warranty, the limitation of our liability, and your obligation to hold us harmless from claims that arise from what you send, what you build, and the people your product shows our answers to.

9. Ending access

We may end your access to the API at any time, for any reason, including breach of these terms. You may stop calling it at any time. Sections 3, 4, 5, 6 and 8 survive.

10. Changes

We may change these API Terms. The date at the top is the date of the current version. Where we have a contact for the key holder we will email material changes first. Calling the API after a change means you accept it.

11. Contact

ARLogic LLC
1705 Nagel St, Saint Marys, OH 45885, United States
legal@fixragent.com