pronto.stream

pronto.stream is a live, cited intelligence wire: hazards and weather, macro releases, market filings, crypto order books, disease surveillance, grid and energy telemetry, space weather, and research publications — hundreds of independent publishers reconciled onto one clock. Unauthenticated callers get 30 calls a minute and 25 rows a response; a dollar of call credits, a day pass or a plan raises both, and Team includes the macro and energy models. The MCP surface is versioned: breaking changes ship behind a new major version. Call get_facet_manifest once to see what the wire carries right now, then scope_signals to select a slice by facet or search_signals to find a subject by word. Search is lexical, not semantic: use the words a source would print. Cite the handle in column 2 of a row and pass it back to get_signal to re-read that one row, or to get_related_signals for the rest of the story. list_fusion_products states the whole derived-product catalogue; get_fused_signal computes what the current window supports, states its formula and cites the signals it came from, and a product with no live inputs says so instead of guessing. If you are refused for a limit rather than for an error, you can buy your way past it with no person involved. The smallest purchase is $1 of call credits: 1,000 calls at $0.001 each, with 600 calls a minute and 100 rows a response while the balance lasts, no expiry, and no charge for a call that returns an error. Builder ($5 a day, $25 a week, $99 a month) and Team ($49 a day, $249 a week, $999 a month) are periods; nothing renews automatically, and buying the same plan again before it ends extends it. Enterprise is a design partner engagement with no list price. To buy: register_agent for an identity; get_plans for every option as data; open_payment with what you are buying and the wallet you will pay from; transfer the exact USDC amount it quotes on Base; then settle_payment with the transaction hash and a personal_sign (EIP-191) signature from that wallet over the SIGN message open_payment returned (smart wallets are checked with ERC-1271). The signature is what proves the transfer is yours: a hash and a sending wallet are public once mined, and neither alone redeems anything. Everything settles in USDC on Base; machine-readable terms are at https://pronto.stream/.well-known/x402. Reading CWF v3. The first lines are the preamble, not data: META states the response-scoped truth. `rows` is what you were given and `matched` is what existed, so if they differ you are holding a sample, not the answer; `truncated:1` says so outright. `span` is the age range the rows cover; if it is hours wide, this is not a picture of right now. `est:N` counts rows whose upstream gave no believable time. `degraded` names sources that were failing, so an absence can be read as an outage rather than as calm. TIME: read `ts:` on the row. It is an absolute Unix epoch and needs no arithmetic. Column 3 is the same instant written as a signed offset from META `t`, for readers that prefer it; you do not need both. `ts:` is always when the observation was made; a forward-looking event carries `sched:` as well, an absolute epoch for when it is scheduled to happen — a launch row is a schedule that was read now, not a launch happening now. SOURCE: read `src:`. When it starts with a REF alias such as `h1/`, the full URL is that REF line's prefix followed by the path. CITE: column 2 is the row's handle. Cite it, and pass it back to get_signal or get_related_signals. Do not read it as data. NUMBERS are labelled on the row itself (`mag:5.8`, `depth_km:29`). A label that is absent means the upstream reported nothing, not zero. SCHEMA lists which numeric labels a signal type can carry, if you want the vocabulary up front. REL states a link between two rows by their handles: echo is the same story from several sources, cross_domain joins two domains. NOTE states something true of the response rather than of a row — a budget that shortened it, or a row that is no longer live. CWF fields are delimited by unescaped pipes `|`. Embedded pipes in text are escaped as `\|`; split fields on unescaped `|` (e.g. tracking preceding backslashes) rather than a simple `split('|')`. Report anything wrong or missing at https://pronto.stream/seo/.

pronto.stream is a live, cited intelligence wire: hazards and weather, macro releases, market filings, crypto order books, disease surveillance, grid and energy telemetry, space weather, and research publications — hundreds of independent publishers reconciled onto one clock. Unauthenticated callers get 30 calls a minute and 25 rows a response; a dollar of call credits, a day pass or a plan raises both, and Team includes the macro and energy models. The MCP surface is versioned: breaking changes ship behind a new major version. Call get_facet_manifest once to see what the wire carries right now, then scope_signals to select a slice by facet or search_signals to find a subject by word. Search is lexical, not semantic: use the words a source would print. Cite the handle in column 2 of a row and pass it back to get_signal to re-read that one row, or to get_related_signals for the rest of the story. list_fusion_products states the whole derived-product catalogue; get_fused_signal computes what the current window supports, states its formula and cites the signals it came from, and a product with no live inputs says so instead of guessing. If you are refused for a limit rather than for an error, you can buy your way past it with no person involved. The smallest purchase is $1 of call credits: 1,000 calls at $0.001 each, with 600 calls a minute and 100 rows a response while the balance lasts, no expiry, and no charge for a call that returns an error. Builder ($5 a day, $25 a week, $99 a month) and Team ($49 a day, $249 a week, $999 a month) are periods; nothing renews automatically, and buying the same plan again before it ends extends it. Enterprise is a design partner engagement with no list price. To buy: register_agent for an identity; get_plans for every option as data; open_payment with what you are buying and the wallet you will pay from; transfer the exact USDC amount it quotes on Base; then settle_payment with the transaction hash and a personal_sign (EIP-191) signature from that wallet over the SIGN message open_payment returned (smart wallets are checked with ERC-1271). The signature is what proves the transfer is yours: a hash and a sending wallet are public once mined, and neither alone redeems anything. Everything settles in USDC on Base; machine-readable terms are at https://pronto.stream/.well-known/x402. Reading CWF v3. The first lines are the preamble, not data: META states the response-scoped truth. `rows` is what you were given and `matched` is what existed, so if they differ you are holding a sample, not the answer; `truncated:1` says so outright. `span` is the age range the rows cover; if it is hours wide, this is not a picture of right now. `est:N` counts rows whose upstream gave no believable time. `degraded` names sources that were failing, so an absence can be read as an outage rather than as calm. TIME: read `ts:` on the row. It is an absolute Unix epoch and needs no arithmetic. Column 3 is the same instant written as a signed offset from META `t`, for readers that prefer it; you do not need both. `ts:` is always when the observation was made; a forward-looking event carries `sched:` as well, an absolute epoch for when it is scheduled to happen — a launch row is a schedule that was read now, not a launch happening now. SOURCE: read `src:`. When it starts with a REF alias such as `h1/`, the full URL is that REF line's prefix followed by the path. CITE: column 2 is the row's handle. Cite it, and pass it back to get_signal or get_related_signals. Do not read it as data. NUMBERS are labelled on the row itself (`mag:5.8`, `depth_km:29`). A label that is absent means the upstream reported nothing, not zero. SCHEMA lists which numeric labels a signal type can carry, if you want the vocabulary up front. REL states a link between two rows by their handles: echo is the same story from several sources, cross_domain joins two domains. NOTE states something true of the response rather than of a row — a budget that shortened it, or a row that is no longer live. CWF fields are delimited by unescaped pipes `|`. Embedded pipes in text are escaped as `\|`; split fields on unescaped `|` (e.g. tracking preceding backslashes) rather than a simple `split('|')`. Report anything wrong or missing at https://pronto.stream/seo/.

pronto.stream is a live, cited intelligence wire: hazards and weather, macro releases, market filings, crypto order books, disease surveillance, grid and energy telemetry, space weather, and research publications — hundreds of independent publishers reconciled onto one clock. Unauthenticated callers get 30 calls a minute and 25 rows a response; a dollar of call credits, a day pass or a plan raises both, and Team includes the macro and energy models. The MCP surface is versioned: breaking changes ship behind a new major version. Call get_facet_manifest once to see what the wire carries right now, then scope_signals to select a slice by facet or search_signals to find a subject by word. Search is lexical, not semantic: use the words a source would print. Cite the handle in column 2 of a row and pass it back to get_signal to re-read that one row, or to get_related_signals for the rest of the story. list_fusion_products states the whole derived-product catalogue; get_fused_signal computes what the current window supports, states its formula and cites the signals it came from, and a product with no live inputs says so instead of guessing. If you are refused for a limit rather than for an error, you can buy your way past it with no person involved. The smallest purchase is $1 of call credits: 1,000 calls at $0.001 each, with 600 calls a minute and 100 rows a response while the balance lasts, no expiry, and no charge for a call that returns an error. Builder ($5 a day, $25 a week, $99 a month) and Team ($49 a day, $249 a week, $999 a month) are periods; nothing renews automatically, and buying the same plan again before it ends extends it. Enterprise is a design partner engagement with no list price. To buy: register_agent for an identity; get_plans for every option as data; open_payment with what you are buying and the wallet you will pay from; transfer the exact USDC amount it quotes on Base; then settle_payment with the transaction hash and a personal_sign (EIP-191) signature from that wallet over the SIGN message open_payment returned (smart wallets are checked with ERC-1271). The signature is what proves the transfer is yours: a hash and a sending wallet are public once mined, and neither alone redeems anything. Everything settles in USDC on Base; machine-readable terms are at https://pronto.stream/.well-known/x402. Reading CWF v3. The first lines are the preamble, not data: META states the response-scoped truth. `rows` is what you were given and `matched` is what existed, so if they differ you are holding a sample, not the answer; `truncated:1` says so outright. `span` is the age range the rows cover; if it is hours wide, this is not a picture of right now. `est:N` counts rows whose upstream gave no believable time. `degraded` names sources that were failing, so an absence can be read as an outage rather than as calm. TIME: read `ts:` on the row. It is an absolute Unix epoch and needs no arithmetic. Column 3 is the same instant written as a signed offset from META `t`, for readers that prefer it; you do not need both. `ts:` is always when the observation was made; a forward-looking event carries `sched:` as well, an absolute epoch for when it is scheduled to happen — a launch row is a schedule that was read now, not a launch happening now. SOURCE: read `src:`. When it starts with a REF alias such as `h1/`, the full URL is that REF line's prefix followed by the path. CITE: column 2 is the row's handle. Cite it, and pass it back to get_signal or get_related_signals. Do not read it as data. NUMBERS are labelled on the row itself (`mag:5.8`, `depth_km:29`). A label that is absent means the upstream reported nothing, not zero. SCHEMA lists which numeric labels a signal type can carry, if you want the vocabulary up front. REL states a link between two rows by their handles: echo is the same story from several sources, cross_domain joins two domains. NOTE states something true of the response rather than of a row — a budget that shortened it, or a row that is no longer live. CWF fields are delimited by unescaped pipes `|`. Embedded pipes in text are escaped as `\|`; split fields on unescaped `|` (e.g. tracking preceding backslashes) rather than a simple `split('|')`. Report anything wrong or missing at https://pronto.stream/seo/.

pronto.stream is a live wire of real-time signals fused from several hundred public sources: seismic, weather and hazard alerts, cyber advisories, disease surveillance, grid and energy telemetry, macroeconomic releases, market and crypto prices, space weather, research publications, and news in many languages. Call search with the words a source would print — matching is lexical, not semantic. Pass a result's id to fetch to read the whole signal. Every result carries a pronto permalink as its url; cite it, and the page it resolves to states the upstream source. fetch returns the signal as a CWF row rather than as a paragraph. Read the guide below once and every row after it reads directly: it is words in labelled fields in a fixed order, and it carries the readings, their units and their absences, which prose about the signal would drop. Reading CWF v3. The first lines are the preamble, not data: META states the response-scoped truth. `rows` is what you were given and `matched` is what existed, so if they differ you are holding a sample, not the answer; `truncated:1` says so outright. `span` is the age range the rows cover; if it is hours wide, this is not a picture of right now. `est:N` counts rows whose upstream gave no believable time. `degraded` names sources that were failing, so an absence can be read as an outage rather than as calm. TIME: read `ts:` on the row. It is an absolute Unix epoch and needs no arithmetic. Column 3 is the same instant written as a signed offset from META `t`, for readers that prefer it; you do not need both. `ts:` is always when the observation was made; a forward-looking event carries `sched:` as well, an absolute epoch for when it is scheduled to happen — a launch row is a schedule that was read now, not a launch happening now. SOURCE: read `src:`. When it starts with a REF alias such as `h1/`, the full URL is that REF line's prefix followed by the path. CITE: column 2 is the row's handle. Cite it, and pass it back to get_signal or get_related_signals. Do not read it as data. NUMBERS are labelled on the row itself (`mag:5.8`, `depth_km:29`). A label that is absent means the upstream reported nothing, not zero. SCHEMA lists which numeric labels a signal type can carry, if you want the vocabulary up front. REL states a link between two rows by their handles: echo is the same story from several sources, cross_domain joins two domains. NOTE states something true of the response rather than of a row — a budget that shortened it, or a row that is no longer live. CWF fields are delimited by unescaped pipes `|`. Embedded pipes in text are escaped as `\|`; split fields on unescaped `|` (e.g. tracking preceding backslashes) rather than a simple `split('|')`. Pronto is a live, cited intelligence wire. Unauthenticated callers get 30 calls a minute and 25 results a response, so a broad query returns a sample of what matched, not all of it. Signals are timestamped and most are minutes old; a few carry an estimated time because the upstream gave none, and the row says which. Feeds come and go with their upstreams, so treat results as live intelligence rather than an archive.

pronto.stream is a live, cited intelligence wire: hazards and weather, macro releases, market filings, crypto order books, disease surveillance, grid and energy telemetry, space weather, and research publications — hundreds of independent publishers reconciled onto one clock. Unauthenticated callers get 30 calls a minute and 25 rows a response; a dollar of call credits, a day pass or a plan raises both, and Team includes the macro and energy models. The MCP surface is versioned: breaking changes ship behind a new major version. Call get_facet_manifest once to see what the wire carries right now, then scope_signals to select a slice by facet or search_signals to find a subject by word. Search is lexical, not semantic: use the words a source would print. Cite the handle in column 2 of a row and pass it back to get_signal to re-read that one row, or to get_related_signals for the rest of the story. list_fusion_products states the whole derived-product catalogue; get_fused_signal computes what the current window supports, states its formula and cites the signals it came from, and a product with no live inputs says so instead of guessing. If you are refused for a limit rather than for an error, you can buy your way past it with no person involved. The smallest purchase is $1 of call credits: 1,000 calls at $0.001 each, with 600 calls a minute and 100 rows a response while the balance lasts, no expiry, and no charge for a call that returns an error. Builder ($5 a day, $25 a week, $99 a month) and Team ($49 a day, $249 a week, $999 a month) are periods; nothing renews automatically, and buying the same plan again before it ends extends it. Enterprise is a design partner engagement with no list price. To buy: register_agent for an identity; get_plans for every option as data; open_payment with what you are buying and the wallet you will pay from; transfer the exact USDC amount it quotes on Base; then settle_payment with the transaction hash and a personal_sign (EIP-191) signature from that wallet over the SIGN message open_payment returned (smart wallets are checked with ERC-1271). The signature is what proves the transfer is yours: a hash and a sending wallet are public once mined, and neither alone redeems anything. Everything settles in USDC on Base; machine-readable terms are at https://pronto.stream/.well-known/x402. Reading CWF v3. The first lines are the preamble, not data: META states the response-scoped truth. `rows` is what you were given and `matched` is what existed, so if they differ you are holding a sample, not the answer; `truncated:1` says so outright. `span` is the age range the rows cover; if it is hours wide, this is not a picture of right now. `est:N` counts rows whose upstream gave no believable time. `degraded` names sources that were failing, so an absence can be read as an outage rather than as calm. TIME: read `ts:` on the row. It is an absolute Unix epoch and needs no arithmetic. Column 3 is the same instant written as a signed offset from META `t`, for readers that prefer it; you do not need both. `ts:` is always when the observation was made; a forward-looking event carries `sched:` as well, an absolute epoch for when it is scheduled to happen — a launch row is a schedule that was read now, not a launch happening now. SOURCE: read `src:`. When it starts with a REF alias such as `h1/`, the full URL is that REF line's prefix followed by the path. CITE: column 2 is the row's handle. Cite it, and pass it back to get_signal or get_related_signals. Do not read it as data. NUMBERS are labelled on the row itself (`mag:5.8`, `depth_km:29`). A label that is absent means the upstream reported nothing, not zero. SCHEMA lists which numeric labels a signal type can carry, if you want the vocabulary up front. REL states a link between two rows by their handles: echo is the same story from several sources, cross_domain joins two domains. NOTE states something true of the response rather than of a row — a budget that shortened it, or a row that is no longer live. CWF fields are delimited by unescaped pipes `|`. Embedded pipes in text are escaped as `\|`; split fields on unescaped `|` (e.g. tracking preceding backslashes) rather than a simple `split('|')`. Report anything wrong or missing at https://pronto.stream/seo/.