API Terms

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.
• Keep your key on your server, in a secret store, and let only the people and systems that need it read it. If you think a key has been exposed, tell us at legal@fixragent.com straight away and stop using it; we will revoke it and issue you a new one. Rotate a key when we ask you to.
• A credential you hold for another platform — a property-management system key, for example — stays yours. If you give one to us so we can do work for you, we use it only for that work, keep it encrypted, and stop using it and delete it when the work ends or you take it back.
• A key is issued on request at /docs#key or /enterprise: enter an email and say in a line what you are building (on /enterprise you also tick the API-terms box); sending the request is your acceptance of these terms, and the key is made when you send and emailed to you. It is for evaluation, on photographs you have the right to send, within the limits the documentation at /docs describes; a production key follows a written agreement. You can also write to legal@fixragent.com.
• 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.
• Do not present an answer as an inspection, a professional opinion, a certification, a finding that a home is or is not legally habitable, a code-compliance finding, or a decision about whether to call emergency services. It is a triage and routing aid: a person on your side makes the call. 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. What you send us

• This section covers everything you send: photos, a resident's own words, and any work-order fields.
• You are responsible for having the right to send each item. Where a photo or a message comes from a resident, you obtain whatever permission the law where they live requires, and you tell them, in your own privacy notice, what happens to it.
• Send only what the read needs. Leave out names, contact details, identity documents, financial or medical details, screens and letters, and any free text that is not about the repair.
• 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; from 6 October 2026 we keep the cleaned photo with the Triage Profile it made (a private store, shown to anyone who has that profile's link), together with its hash, the answer, and the versions that produced it. Send keep_photo: false in the request body to have the photo not kept.
• For the read itself we act on your instructions. What we may keep and use afterwards is set out 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 what you send through the API, with three limits that come first:

• A signed agreement controls. Where your organisation has a signed written agreement with AR Logic, that agreement governs how we use the data it covers.
• No cross-customer training on identifiable resident or work-order data. We do not use identifiable resident or work-order data you send to train or improve the engine for other businesses unless you have expressly authorised it in writing.
• De-identified means really de-identified. Any improvement or aggregate use starts from data that cannot reasonably be linked to a person or household in context: we remove or generalise names, contact details, addresses, property and unit identifiers, free text and image metadata, and we do not try to re-identify it.

The outcome callback. The diagnosis_id we return is the key that joins an outcome to its read. The callback takes a defined set of fields — the diagnosis_id, the outcome, how it was reported, who fixed it, the trade, short free-text fields for the parts and the fix, and optionally the email of the account it belongs to — and outcomes you post become part of the same record. Sending us an outcome is not permission to take anything else: access to a work order does not let us read its later notes, bills or resident messages beyond what a signed agreement lists.

Other platforms. We receive only the rights you are able to give us. A key or credential you hold for a property-management platform does not, by itself, show that the platform allows a third party to access it, to keep learning from its data, or to use its name, and these terms create no right against that platform.

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 is a separate written agreement between you and AR Logic, and nothing here creates one. That agreement sets out the price and any overage, billing and taxes, the term and renewal, rate limits and any service level, support, the data terms, security, who holds what rights in the output, the warranty, liability and indemnity, how changes are made, and how access ends.

8. Warranty, liability and your responsibility to others

Sections 9, 10 and 11 of the Terms of Service apply to free use of the API: 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. For a paying business, the liability and indemnity terms in the signed agreement apply instead.

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.

When a paid or pilot arrangement ends, we close it in order: we revoke the keys, stop any scheduled reads, and delete or return the identified data we hold for you. We keep only what the law or security requires and what has already been de-identified. Sections 3, 4, 5, 6 and 8 survive.

10. Open-source client code

Our MCP server and SDK client code carry the MIT licence, copyright AR Logic LLC. That licence covers the client code only. It does not give you a key, access to the API, any service, or any right in the answers the API returns; those come only from these terms.

11. 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 for what you send from then on. A change here does not widen what we may do with data you have already sent, and it never overrides a signed agreement.

12. Contact

AR Logic LLC
legal@fixragent.com