Terms of Service
For the free public REST APIs at aisenseapi.com/services/v1. Custom API work is covered by its own written agreement, not by this page.
Last updated 9 September 2026.
What you are getting
A set of utility endpoints, provided by AI SENSE AS (Postboks 1202 Vika, 0110 Oslo, Norway, org.nr NO 922 601 151 MVA), free of charge and without registration. Using them means accepting what is on this page. If you do not, do not call them.
They are published under the MIT licence together with client libraries and tests at github.com/aisenseapi/aisense-free-public-rest-apis. That licence covers the code we publish, not the operation of this service.
Limits
5000 requests per IP address per day. Beyond that you receive HTTP 429 until the shared counter resets at midnight Norwegian time (Europe/Oslo). This is not a rolling per-request window. The limit is a technical control. We may change it.
80 MB of stored data per IP address per day on /storage, counted on the same calendar day and reset together with the request counter. Executable files are refused at upload.
Active data has a 24-hour ceiling in /storage, /url_shortener, /webhook_capture, /webhook_action, /agent_wake, /heartbeat, /lease, /inbox, /dns and /semantic_search. Agent Wake may use a shorter timeout. A Heartbeat terminal record can remain readable for another 24 hours after its target data has been removed. A Lease has a fixed absolute expiry 24 hours after the first acquisition, and renewals cannot extend it. Webhook Schedule keeps its final result for up to 24 hours after the delivery attempt.
Agent Queue and all associated payloads, deduplication entries, completed jobs and failed jobs expire exactly 24 hours after queue creation. No activity extends that deadline. Each queue accepts up to 100 distinct jobs over its lifetime, 16 KiB of encoded JSON per payload and five claim attempts per job. New queues are limited to 20 per client IP per 24 hours.
Jobs can be delivered again after a claim expires or is released. Queue expiry and the attempt limit may leave jobs unfinished. Initial delivery and exactly-once execution are not guaranteed. Make external actions idempotent. The service does not execute jobs, fetch payload URLs or send callbacks.
Semantic search collections, their notes and vectors expire exactly 24 hours after creation. No activity extends that deadline. Each collection accepts up to 500 notes over its lifetime, deleted notes included, and new collections are limited to 20 per client IP per 24 hours. A search answers ranked suggestions with scores, not a decision that a match exists, and you remain responsible for what you do with a result. Note content stays yours. Keep the read and write tokens private: anyone holding the read token can search the notes.
Queue content also stays yours. Its separate read, write and worker tokens grant access only to their corresponding operations. Workers receive payloads when claiming. Keep these tokens and claim receipts private. A queue ID alone does not authorize access. The Queue service writes payload content to its JSON state files without encrypting it. It normalizes object-key ordering and JSON serialization.
This is not storage you can rely on
The temporary endpoints exist for moving data between steps of a process, not for keeping it. Keep your own copy of anything you cannot afford to lose. Data may become unavailable before the 24 hours elapse - a restart, a fault or maintenance will do it - and we will not be able to recover it for you.
No warranty and no service level
The service is provided as-is and as-available. We do not promise it will be up, that it will be correct, that it will be fast, or that it will continue to exist. There is no uptime commitment, no support obligation and no notice period. We may change, limit or withdraw any endpoint at any time, including permanently and without warning.
To the extent Norwegian law allows, AI SENSE AS is not liable for any loss arising from use of these APIs or from their unavailability - including lost data, lost profit, lost business or any indirect or consequential loss. Nothing here limits liability that cannot lawfully be limited.
If your system would suffer materially from these endpoints being unavailable, do not build on them. Choose infrastructure with suitable availability commitments if your workflow needs them. This repository publishes documentation and client libraries, not the complete service backend.
Wallet generation
The wallet endpoints are for development and testing only. They generate a private key on our server and send it to you over the internet. A key produced that way has crossed infrastructure that neither you nor we fully control, and it has existed in memory on a shared public service.
Never place funds in a wallet generated by these endpoints. If you do so anyway, any loss is yours. Balance lookups are informational and may be wrong, stale or unavailable - they depend on third-party blockchain services that we do not operate.
Acceptable use
Do not use these APIs to break the law, to attack or disrupt this service or anyone else's, to circumvent the rate limit by rotating addresses, or to store or transmit unlawful material. Do not use the storage or webhook endpoints to hold personal data belonging to other people beyond what your own lawful purpose requires - you are the one responsible for that data, not us.
Do not present this service as your own to your users in a way that leaves them relying on it without knowing.
We may block an address or withdraw access where use is unlawful, abusive or threatens availability for others, and we may do so without notice.
Content on /storage that is reported to abuse@aisense.no as unlawful or abusive is removed when we receive the notice, and the address that posted it may be blocked.
Content you send
Whatever you post to the storage or webhook endpoints stays yours. We claim no rights in it. We store it for the stated period so that we can hand it back to you, and we do nothing else with it. See the Privacy page for what is recorded and for how long.
For Storage, Capture, Approval, Schedule, Agent Wake, Heartbeat and Inbox reads, the relevant bearer ID or link authorizes access. Anyone holding that value can read the associated state, so treat it as a secret. Lease and Queue have their own operation-specific access rules. Queue requires the corresponding read, write or worker token, and a queue ID alone grants no access.
Third parties
Some endpoints contact another service in order to answer you, including blockchain data providers for balance lookups. Short-link creation stores its mapping within this service and does not call a separate redirect provider. Webhook Schedule, Heartbeat and optional Capture or Approval notifications can send requests to public URLs you choose. Agent Inbox receives mail through the configured mail provider. External services have their own terms and availability, and we make no promises on their behalf. The full list is on the Privacy page.
Changes
These terms may change. The date at the top is the last revision. Continuing to call the APIs after a change means accepting it, since there is no account through which we could notify you.
Governing law
Norwegian law applies. Disputes belong to the Norwegian courts, with Oslo tingrett as the agreed venue at first instance. This does not remove any right a consumer has to bring proceedings where they live.
Contact
support@aisense.no, or the Contact Us page.