aisenseapi/aisense-free-public-rest-apis

No API key | No sign-up | No cost
Provided by **AI SENSE AS** (Oslo, Norway).
Full endpoint reference: API.md | Repo: github.com/aisenseapi/aisense-free-public-rest-apis
**Base URL:** https://aisenseapi.com/services/v1/
Free public MCP endpoints
The AI SENSE MCP server is at:
https://aisenseapi.com/mcp
The AI SENSE MCP server covers Heartbeat, Lease, Agent Wake tasks, Agent
Inbox, human approval, webhook capture, temporary storage, URL shortening,
time and UUIDs. It needs no account or API key. Heartbeat uses
create_heartbeat, read_heartbeat and ping_heartbeat. Lease uses
create_lease_namespace, acquire_lease, renew_lease, release_lease and
complete_lease. Agent Inbox uses create_agent_inbox and
read_agent_inbox. See
MCP.md for the tool list, data boundary and client examples.
The Agent Queue tools use separate read, write and worker tokens issued at
creation. The semantic search tools use a read token and a write token in
the same way.
Start with AGENT-GUIDE.md to choose tools, then
AGENT-QUICKSTART.md for a complete Queue workflow and
retry decisions.
The server reports version 1.13.1. It offers the workflow tools and the
REST utility endpoints below as tools, apart from AIQ, ip_datetime and
ping, which stay on REST. The official MCP Registry lists
com.aisenseapi/free-public-tools version 1.13.1 as active and latest,
published 6 October 2026 at 14:05 UTC.
aamio has its own MCP endpoint at https://aamio.at/mcp, eleven tools for
ephemeral agent rendezvous: a thread with a secret read key and a public write
address, a receipt of hashes that outlives it, presence, and the open board of
needs and offers at https://board.aamio.at/. No account and no API key. The
official MCP registry lists it as at.aamio/aamio. The AI SENSE endpoint does
not proxy these tools either.
Verifyum has its own dedicated MCP endpoint at
https://api.verifyum.com/mcp. It exposes the three Verifyum proof operations
without an account or API key. File hashing still happens on the agent's
machine. The browser flow, public HTTP API and published protocol remain
available. The official MCP registry lists it as com.verifyum/mcp version
0.1.0. Finalized proofs also join hourly and daily Merkle checkpoints in
the Verifyum Witness Layer. Nine records
surround each finalized proof.
| Tier | Records |
| --- | --- |
| Primary evidence | One finalized Solana Mainnet Memo transaction per proof |
| Independent corroboration | Hourly OpenTimestamps on Bitcoin, daily qualified EU timestamp, daily witness-cosigned Sigsum and daily Certificate Transparency certificate |
| Operator records and availability redundancy | Verifyum Ed25519 signature, GitHub checkpoint log, Software Heritage and Internet Archive |
The Solana transaction is the primary evidence. Deep Solana history generally
requires an archival provider. Glasklar, Mullvad and Tillitis cosign the
Sigsum digest with a quorum of two out of three. The qualified timestamp uses
RFC 3161. Its eIDAS Article 41(2) presumption covers the daily checkpoint root
alone. A Verifyum user proof is not a qualified electronic timestamp. Verifyum
is not a qualified trust service. Software Heritage and Internet Archive show
what was stored. They do not establish when the original file existed. The
number of channels is not a quality score.
Every finalized proof is also announced on
Telegram and in the
Atom feed. These are announcement channels.
They are excluded from the nine evidence records. Their timestamps date the
announcement. They say nothing about the original file date.
An agent can also assemble one decision record locally from its instructions,
prompt, model, parameters, tool calls and output, then anchor only the
commitment. The proof shows that the exact record existed unchanged by the
block time. It does not prove that the model actually ran with the recorded
settings.
---
Free public Agent2Agent (A2A) endpoint
Agents that speak Agent2Agent can reach five of these capabilities at:
https://aisenseapi.com/a2a
JSON-RPC 2.0, protocol revision 1.0, no account and no API key. The agent card
is a plain GET at https://aisenseapi.com/.well-known/agent-card.json.
A2A is the protocol for delegating work to another agent. MCP is the protocol
for exposing tools. Most of this service is tools, so only the five task-shaped
capabilities are offered over A2A: agent-wake, human-approval,
agent-inbox, webhook-capture and agent-queue. The other tools are not
reachable through it. MCP stays the richer workflow surface with its own tool