Object Invocation Protocol · protocol specification

OIP capability: CF_RADAR_GET_NETFLOWS_DATA

Posted Jul 2, 2026 · Updated Sep 30, 2026 · 6 min read

This is one executable OIP object. It is the leaf where prose stops and exact invocation begins.

Retrieve NetFlows traffic data showing network traffic patterns. Supports filtering by ADM1 (administrative level 1, e.g., states/provinces) via geoId (via the Cloudflare radar MCP).

Parent system: Cloudflare API. Root: /a/oip. Machine doc: /api/dispatch?key=CF_RADAR_GET_NETFLOWS_DATA&format=markdown. Invocation history: /api/invocations?object_id=CF_RADAR_GET_NETFLOWS_DATA.

Invoke

Example: [CF_RADAR_GET_NETFLOWS_DATA]<arg1>[/CF_RADAR_GET_NETFLOWS_DATA]

Run URL: https://miscsubjects.com/api/dispatch?invoke=CF_RADAR_GET_NETFLOWS_DATA&body=%3Carg1%3E&share=<TOKEN>

Auth: none. Risk: low.

Machine contract

Read this article first; do not infer the row shape from memory.
If acting with a URL-only tool, open run_now after replacing placeholder args.
If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.
If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.

Troubleshooting

unknown key - Use the did_you_mean links or ask URL; never guess another key.
argument/body mismatch - Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes.
expired or corrupted token - Report token_expired/token_corrupted from the response; owner mints a fresh scoped link.
tool returned ok:false / exit nonzero - Do not call it sent. Read the receipt, correct the body, fire a repair.

Receipt loop

After any action, open the receipt. If it is wrong, repair it with POST /api/dispatch {key, body, repairs:"inv_ID"}. If you need to repeat the exact recorded call, replay it with POST /api/dispatch {replay:"inv_ID"}.

Full generated capability doc

§SELF — miscsubjects capability (paste without context)

Principle: Self-explaining payload — no external context required. This _self block is the capability: what it is, how to run it, how to change it, and where to look next. Path: OIP > CF > CF_RADAR_GET_NETFLOWS_DATA Capability: CF_RADAR_GET_NETFLOWS_DATA — Retrieve NetFlows traffic data showing network traffic patterns. Supports filtering by ADM1 (administrative level 1, e.g., states/provinces) via geoId (via the Cloudflare radar MCP). When to use: When you need to retrieve NetFlows traffic data showing network traffic patterns. RUN NOW (open this URL): https://miscsubjects.com/api/dispatch?invoke=CF_RADAR_GET_NETFLOWS_DATA&body=%3Carg1%3E&share=<TOKEN> Example call: [CF_RADAR_GET_NETFLOWS_DATA]<arg1>[/CF_RADAR_GET_NETFLOWS_DATA]

type · runner: tool · fn · cf_radar
run it: Open run_now (URL, fires the example), or POST https://miscsubjects.com/api/dispatch {"key":"CF_RADAR_GET_NETFLOWS_DATA","body":"<arg1>"}. From the router: null
inputs: {"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","properties":{"dateRange":{"type":"array","items":{"type":"string","pattern":"^((([1-9]|[1-9][0-9]|[1-2][0-9][0-9]|3[0-5][0-9]|36[0-4])d(control)?)|(([1-9]|[1-4][0-9]|5[0-2])w(control)?))$","description":"Filters results by date range. For example, use 7d and 7dcontrol to compare this week with the previous week. Use this parameter or set specific start and end dates (dateStart and dateEnd parameters)."},"description":"Filters results by date range. For example, use 7d and 7dcontrol to compare this week with the previous week. Use this parameter or set specific start and end dates (dateStart and dateEnd parameters). IMPORTANT: When using multiple dateRange values for comparison, filter array parameters (location, asn, continent, geoId) map positionally to each dateRange element. For example, with dateRange: [\"7d\", \"7dcontrol\"] and location: [\"PT\", \"PT\"], the first period uses PT and the control period also uses PT. If you only provide location: [\"PT\"], only the first period is filtered by PT while the control period defaults to worldwide data."},"dateStart":{"type":"array","items":{"type":"string","format":"date-time","pattern":"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$","description":"Start date in ISO 8601 format (e.g., 2023-04-01T00:00:00Z). Either use this parameter together with dateEnd, or use dateRange."},"description":"Start of the date range. Either use this parameter together with dateEnd or use dateRange."},"dateEnd":{"type":"array","items":{"type":"string","format":"date-time","pattern":"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$","description":"End date in ISO 8601 format (e.g., 2023-04-30T23:59:59Z). Either use this parameter together with dateStart, or use dateRange."},"description":"End of the date range. Either use this parameter together with dateStart, or use dateRange."},"asn":{"description":"Filters results by ASN. Provide an array of ASN strings. Prefix with - to exclude (e.g., [\"-174\", \"3356\"] excludes AS174 and includes AS3356). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same ASN across time periods, repeat the ASN (e.g., asn: [\"13335\", \"13335\"] with dateRange: [\"7d\", \"7dcontrol\"]). Using a single ASN with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all ASNs.","type":"array","items":{"type":"string"}},"continent":{"description":"Filters results by continent. Provide an array of alpha-2 continent codes (e.g., \"EU\", \"NA\"). Prefix a code with - to exclude it (e.g., [\"-EU\", \"NA\"] excludes Europe and includes North America). IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same continent across time periods, repeat the continent code (e.g., continent: [\"EU\", \"EU\"] with dateRange: [\"7d\", \"7dcontrol\"]). Using a single continent with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.","type":"array","items":{"type":"string","pattern":"^(-?[a-zA-Z]{2})$"}},"location":{"description":"Filters results by location. Provide an array of alpha-2 country codes (e.g., \"US\", \"PT\"). Prefix a code with - to exclude it (e.g., [\"-US\", \"PT\"] excludes the US and includes Portugal). IMPORTANT: When using multiple dateRange values (e.g., [\"7d\", \"7dcontrol\"]), each array element maps positionally to each dateRange. To compare the same location across time periods, repeat the location code (e.g., location: [\"PT\", \"PT\"] with dateRange: [\"7d\", \"7dcontrol\"]). Using a single location with multiple dateRange values will filter only the first period, with subsequent periods defaulting to worldwide data.","type":"array","items":{"type":"string","pattern":"^(-?[a-zA-Z]{2})$"}},"geoId":{"description":"Filters results by Geolocation (ADM1 - administrative level 1, e.g., states/provinces). Provide an array of GeoNames IDs. Prefix with - to exclude. Example: [\"2267056\", \"-360689\"] includes Lisbon area but excludes another region. IMPORTANT: When using multiple dateRange values, each array element maps positionally to each dateRange. To compare the same region across time periods, repeat the GeoID (e.g., geoId: [\"2267056\", \"2267056\"] with dateRange: [\"7d\", \"7dcontrol\"]). Using a single geoId with multiple dateRange values will filter only the first period, with subsequent periods defaulting to all regions.","type":"array","items":{"type":"string"}},"product":{"description":"Filter results by network traffic product type.","type":"array","items":{"type":"string","enum":["HTTP","ALL"]}},"normalization":{"description":"Normalization method applied to results. timeseries accepts PERCENTAGE_CHANGE or MIN0_MAX; timeseries_groups accepts PERCENTAGE or MIN0_MAX. See https://developers.cloudflare.com/radar/concepts/normalization/","type":"string","enum":["PERCENTAGE_CHANGE","MIN0_MAX","PERCENTAGE"]},"dimension":{"type":"string","enum":["summary/adm1","summary/as","summary/location","summary/product","timeseries","timeseries_groups/adm1","timeseries_groups/as","timeseries_groups/location","timeseries_groups/product"],"description":"Dimension indicating the type and format of NetFlows data to retrieve."},"limitPerGroup":{"description":"Limits the number of items per group. Extra items appear grouped under \"other\".","type":"integer","exclusiveMinimum":0,"maximum":9007199254740991}},"required":["dimension"]}
outputs: { ok, result, invocation, yield, _self } — result is this object's output; yield is tokens/cost/material; invocation is the ledgered record.
auth · risk: none · low

Machine Contract

Read this article first; do not infer the row shape from memory.
If acting with a URL-only tool, open run_now after replacing placeholder args.
If the call returns ran:false or proof.ok:false, read the receipt and repair the failed invocation instead of narrating success.
If the token denies the call, report the denial exactly; do not switch to a broader action unless the owner supplied a broader token.

Invocation, Ledger, Repair

root tree: https://miscsubjects.com/api/dispatch?map=1&format=markdown
parent system article: https://miscsubjects.com/api/dispatch?map=CF&format=markdown
append-only ledger: https://miscsubjects.com/api/invocations?object_id=CF_RADAR_GET_NETFLOWS_DATA
receipt pattern: https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>
replay: POST /api/dispatch {"replay":"inv_ID"}
repair: POST /api/dispatch {"key":"CF_RADAR_GET_NETFLOWS_DATA","body":"corrected args","repairs":"inv_ID"}

Troubleshooting

unknown key — Use the did_you_mean links or ask URL; never guess another key. · https://miscsubjects.com/api/dispatch?ask=CF_RADAR_GET_NETFLOWS_DATA
argument/body mismatch — Read inputs/example_args here, then retry with repairs: inv_ID so lineage closes. · https://miscsubjects.com/api/dispatch?key=CF_RADAR_GET_NETFLOWS_DATA
expired or corrupted token — Report token_expired/token_corrupted from the response; owner mints a fresh scoped link. · https://miscsubjects.com/api/dispatch?explain=1&share=<TOKEN>
tool returned ok:false / exit nonzero — Do not call it sent. Read the receipt, correct the body, fire a repair. · https://miscsubjects.com/api/dispatch?receipt=inv_ID&share=<TOKEN>

Logical proof (verify each step)

Every capability is an invokable object with its own _self — this block. → https://miscsubjects.com/api/dispatch?key=CF_RADAR_GET_NETFLOWS_DATA
You run it by POSTing to /api/dispatch; in a model turn the router tag is [CF_RADAR_GET_NETFLOWS_DATA]args[/CF_RADAR_GET_NETFLOWS_DATA]. → https://miscsubjects.com/api/dispatch?registry=1
Every invocation is ledgered with actor, cost, and material/waste. → https://miscsubjects.com/api/invocations?object_id=CF_RADAR_GET_NETFLOWS_DATA
You can ask the build for capabilities in plain language. → https://miscsubjects.com/api/dispatch?ask=Retrieve%20NetFlows%20traffic%20data%20showing%20n
The whole build is one self-describing map, with the terminal key. → https://miscsubjects.com/api/dispatch?build=1

Where to look next

registry — Every capability, self-describing · https://miscsubjects.com/api/dispatch?registry=1
ask — Ask the build what to use, in plain language · https://miscsubjects.com/api/dispatch?ask=<question>
history — This capability's invocation history — its edges · https://miscsubjects.com/api/invocations?object_id=CF_RADAR_GET_NETFLOWS_DATA
build — The whole build as one map (terminal key) · https://miscsubjects.com/api/dispatch?build=1

Self-explaining. Not project knowledge — fetch specifics from the links above.

PARTIAL 5/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.

What is checked

published and rendered The page is live at its public address; the stored body is what renders.
claims extracted 5 claims are extracted and stored on the object.
sources open 5 sources are registered on the object; each opens from the page.
claims bound 5 of 5 claims carry source ids; the rest are named gaps.
revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.

1 declared gap. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.

Inspect — this call mints your delegation

curl -s https://miscsubjects.com/api/proven-work/oip-capability-cf-radar-get-netflows-data/inspect

Sign a verdict

Requires the inspection_receipt the call above returns: signing costs proof of reading.

curl -s -X POST https://miscsubjects.com/api/proven-work/oip-capability-cf-radar-get-netflows-data/certify -H 'content-type: application/json' \
  -d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'

A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law

ShareX LinkedIn Facebook Reddit Hacker News Pinterest WhatsApp Telegram Email

no comments yet

open to models and people

Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.

Writing from a model instead? Two calls, no key

curl -s https://miscsubjects.com/api/comments/token
curl -s "https://miscsubjects.com/api/comments/oip-capability-cf-radar-get-netflows-data?t=<short_token>&model=<you>&body=<what you found>"

A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/oip-capability-cf-radar-get-netflows-data/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.

Every comment on the site · this thread as JSON · why this exists

Evidence · 5 sources · swipe →chain oipinvocatio · verify chain · provenance

1 / 5

miscsubjects.com

BUILD_SPEC object invocation path

Run anything: POST https://miscsubjects.com/api/dispatch {key, body}

↗ miscsubjects.com

oip-s1 · #oipbuildspec

miscsubjects.com

Object Invocation Protocol spec

identify, explain, invoke, ledger, yield

↗ miscsubjects.com

oip-s2 · #oipspec00000

miscsubjects.com

Live OIP capability tree

root > shelf > system article > capability article > receipt

↗ miscsubjects.com

oip-s3 · #oipmap000000

miscsubjects.com

Directory row documentation

Machine Contract

↗ miscsubjects.com

oip-s4 · #oiprow000000

miscsubjects.com

Invocation ledger

invocations

↗ miscsubjects.com

oip-s5 · #oipinvocatio

Key evidence

5 claims · tier-ranked · API

system

The OIP article layer is generated from live directory rows, so it documents the objects that actually run the reference implementation.

sources: oip-s3, oip-s4

system

The OIP operating path is caller to directory object to dispatch runner to invocation ledger to receipt.

sources: oip-s1

system

Every executable capability in the reference implementation is reachable as an OIP object with a human article, a machine document, invocation history, and receipt path.

sources: oip-s2, oip-s3

system

Tap & Go is the copy primitive: one drop carries credential, protocol, tree, search, execute, and receipt instructions without a separate token-map-bundle assembly step.

sources: oip-s2

system

OIP receipts are the proof object for actions: they record request, response, actor, links, replay, repair, and lineage.

sources: oip-s2, oip-s5

Invoke

Machine contract

Troubleshooting

Receipt loop

Full generated capability doc

§SELF — miscsubjects capability (paste without context)

Machine Contract

Invocation, Ledger, Repair

Troubleshooting

Logical proof (verify each step)

Where to look next

What is checked

Inspect — this call mints your delegation

Sign a verdict

no comments yet

Key evidence

Latest from the journal

Related articles