ChronicaPulse: Global genealogy and historical archive intelligence API. Full-text search across Chronicling America (1770–1963 US newspapers), Library of Congress, Trove (Australia), British Newspaper Archive, Euro Coverage: Global Endpoints: • search ($0.05): Archive search • person ($0.12): Pe...
AI agents call chronicapulse to retrieve information from Pulsenetwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Search query |
era | string | — | era |
lang | string | — | lang |
name | string | — | name |
type | string | — | type |
year | string | — | year |
event | string | — | event |
place | string | — | place |
state | string | — | state |
action | string | Yes | Which endpoint to call. Options: search | person | obituary | event | place | immigration | military | business | timeline |
origin | string | — | Country of origin |
subject | string | — | subject |
Parameters from the server's own tool schema.
ChronicaPulse provides read-only access to historical archives and genealogical databases. Users can search and retrieve information but cannot modify, delete, or execute arbitrary operations. While the server charges per query (x402 USDC payment), the tool itself does not move money—the payment is infrastructure-level.
From the tool's definition All endpoints are query/search operations: 'search', 'person research', 'obituary research', 'historical event coverage', 'place history', 'immigration research', 'military service research', 'business history', 'timeline'.
Risk signalsAccepts file system path (destination) · High parameter count (18 properties)
Attacks that exploit this kind of access
ChronicaPulse: Global genealogy and historical archive intelligence API. Full-text search across Chronicling America (1770–1963 US newspapers), Library of Congress, Trove (Australia), British Newspaper Archive, Euro Coverage: Global Endpoints: • search ($0.05): Archive search • person ($0.12): Person research • obituary ($0.10): Obituary research • event ($0.08): Historical event coverage • place ($0.08): Place history • immigration ($0.12): Immigration research • military ($0.10): Military service research • business ($0.08): Business history • timeline ($0.15): Chronological timeline. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
chronicapulse accepts 12 parameters: q, era, lang, name, type, year, event, place, state, action, origin, subject. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for chronicapulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.
chronicapulse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the chronicapulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for chronicapulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
chronicapulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
chronicapulse is one line of Pulsenetwork's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →