Onrender APIinf-tracer-rh3o.onrender.com ↗
Access bitemporal audit trail data from INF Tracer agent sessions: event timelines, hash chain proofs, and integrity verification across 4 endpoints.
What is the Onrender API?
The INF Tracer API exposes 4 endpoints for reading audit trail data from agent sessions, covering event timelines, hash chain integrity, and full audit document exports. The get_timeline endpoint returns every agent event — memory writes, LLM calls, tool uses, and decisions — in chronological order alongside memory snapshots. The get_audit endpoint combines all of that with a cryptographic chain proof into a single exportable document suitable for offline verification.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/026191c0-de22-4368-a67b-51f0f231157b/get_timeline' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace inf-tracer-rh3o-onrender-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: INF Tracer SDK — bitemporal audit trail access, bounded and re-runnable."""
from parse_apis.inf_tracer_rh3o_onrender_com_api import InfTracer, ParseError
client = InfTracer()
# Quick integrity check — single call, typed fields.
session = client.sessions.get()
print(f"Agent: {session.agent_id}, Integrity: {session.integrity}, Chain: {session.chain_length} blocks")
# Walk the event timeline — limit caps total items fetched.
for event in client.sessions.timeline(limit=5):
print(f" [{event.event_type}] {event.summary} @ {event.timestamp_iso}")
# Retrieve the full chain proof for cryptographic verification.
proof = client.sessions.chain()
print(f"Chain verified: {proof.integrity}, genesis={proof.genesis_hash[:16]}…, head={proof.head_hash[:16]}…")
# Full audit document — comprehensive export with nested typed resources.
try:
doc = client.sessions.audit()
print(f"Audit exported at {doc.export_time}, {doc.event_count} events, integrity={doc.integrity.integrity}")
except ParseError as exc:
print(f"Audit retrieval failed: {exc}")
print("exercised: sessions.get / sessions.timeline / sessions.chain / sessions.audit")
Retrieves the full agent event timeline for the current session. Returns all events (memory writes, LLM calls, tool uses, decisions) in chronological order with their associated memory snapshots at each point in time.
No input parameters required.
{
"type": "object",
"fields": {
"count": "integer",
"events": "array of event objects containing event_id, event_type, timestamp_iso, data, memory_snapshot, and summary",
"agent_id": "string"
},
"sample": {
"data": {
"count": 17,
"events": [
{
"data": {
"key": "applicant_id",
"value": "app_gemini_882",
"old_value": null
},
"hash": null,
"summary": "Memory updated: applicant_id = app_gemini_882",
"agent_id": "credit-underwriter-production-session",
"event_id": "evt-975f962509a3",
"timestamp": 1782566401.4305706,
"event_type": "memory_write",
"timestamp_iso": "2026-06-27T13:20:01.430571+00:00",
"memory_snapshot": {
"applicant_id": "app_gemini_882"
}
}
],
"agent_id": "credit-underwriter-production-session"
},
"status": "success"
}
}About the Onrender API
Event Timeline and Session Data
The get_timeline endpoint returns the complete ordered sequence of events recorded for the current agent session. Each event object includes an event_id, event_type, ISO-formatted timestamp_iso, a data payload, a memory_snapshot capturing state at that point in time, and a summary field. The response also surfaces the agent_id and a total count of events. This gives you a full bitemporal view of what happened during a session and what the agent's memory state looked like at each step.
Hash Chain Integrity Verification
Two endpoints handle cryptographic verification. get_integrity returns a quick status check: the agent_id, current head_hash, an integrity status string, and both chain_length and event_count integers. For deeper verification, get_chain returns the complete hash chain including the genesis_hash, head_hash, a verified_at Unix timestamp, and the full hash_sequence — an ordered array of SHA-256 hex strings representing every block fact hash in the chain. This lets you independently replay and verify the chain without trusting the service's integrity status alone.
Complete Audit Export
get_audit is the all-in-one export endpoint. Its response bundles the full events array, the agent_id, an integrity object with verification status, a chain_proof object containing the complete hash_sequence, an event_count, and an export_time string. The document is structured for offline cryptographic verification — you get everything needed to validate both the event data and its hash chain provenance in a single response.
Session Scope
All four endpoints operate against the current agent session; there are no input parameters to filter by date range, event type, or agent identifier. The session context is implicit in the request, so each call reflects the state of the running session at the time it is made.
The Onrender API is a managed, monitored endpoint for inf-tracer-rh3o.onrender.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when inf-tracer-rh3o.onrender.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official inf-tracer-rh3o.onrender.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Verify the integrity of an AI agent's decision log by replaying the SHA-256 hash sequence from
get_chain - Reconstruct the memory state of an agent at a specific point in time using
memory_snapshotfields fromget_timeline - Export a tamper-evident audit document via
get_auditfor compliance or legal review - Monitor session health by polling
get_integrityfor chain validity and event count without fetching the full event list - Audit which tool calls and LLM invocations occurred during a session using
event_typefields in the timeline - Archive the genesis-to-head hash chain for long-term cryptographic provenance records using
get_chainoutput
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does INF Tracer have an official developer API?+
What does `get_chain` return beyond what `get_integrity` provides?+
get_integrity returns a summary — head_hash, integrity status, chain_length, and event_count — suitable for a quick validity check. get_chain adds the genesis_hash, a verified_at timestamp, and the full hash_sequence array of SHA-256 hashes, which is what you need to independently replay and verify the entire chain block by block.Can I filter events by event type or date range?+
get_timeline and get_audit always return the complete event set for the current session. You can fork this API on Parse and revise it to add filtering logic by event_type or timestamp_iso range.Can I retrieve audit data for past sessions or a specific agent by ID?+
agent_id. You can fork this API on Parse and revise it to add session-selection endpoints if the underlying source supports it.Is the `integrity` field in `get_audit` the same as the one in `get_integrity`?+
get_integrity returns integrity as a plain string status. In get_audit, integrity is an object that may carry additional verification metadata alongside the status. Use get_integrity for lightweight polling and get_audit when you need the full document for offline verification.