Dynamic Feed Robot API

The robot API from Dynamic Feed — 10 operation(s) for robot.

Operations 10

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /v1/anchor/daily Get the RFC 3161 anchor for a day's snapshot · V1 Anchor Daily #
Ask an LLM
“Is each day's world-state snapshot timestamped so I can prove what was reported?”
“Can I fetch the daily anchor proof for a past date?”
Tell an agent
Get the daily anchor proof for {date}.
Anchor today's world-state snapshot and return its timestamp proof.
POST /v1/awareness Get a go/no-go verdict for a robot at a location · V1 Awareness #
Ask an LLM
“Can one call tell my robot whether it is safe to operate at a location?”
“What happens to the verdict when some feeds time out and the snapshot is degraded?”
Tell an agent
Get a situational-awareness verdict for my orbital robot at its current location.
Run a general awareness check for any robot class at these coordinates.
POST /v1/preflight Run a drone pre-flight safety check · V1 Preflight #
Ask an LLM
“Is it safe to fly my drone here right now given wind, air quality and space weather?”
“Does the drone pre-flight check consider GPS integrity?”
Tell an agent
Run a drone pre-flight check at my launch site.
Give me a take-off verdict for my aerial drone at these coordinates.
POST /v1/road Check road hazards for an autonomous vehicle · V1 Road #
Ask an LLM
“Are there weather or earthquake hazards along my autonomous vehicle's route?”
“What go or no-go verdict does the ground vehicle check return?”
Tell an agent
Run a road hazard check for my ground vehicle at this location.
Check over-the-horizon hazards for an autonomous car near these coordinates.
POST /v1/humanoid Run a humanoid robot pre-operation check · V1 Humanoid #
Ask an LLM
“Is it safe for my humanoid robot to work among people given wind and icy ground?”
“Which conditions does the humanoid check weigh, like topple risk and slipping?”
Tell an agent
Run a humanoid pre-operation check at this site.
Give my bipedal robot a go or no-go verdict for its work location.
POST /v1/marine Run a marine vessel pre-operation check · V1 Marine #
Ask an LLM
“Is wave height too high for my uncrewed surface vessel to operate today?”
“Does the marine check account for tsunami risk from nearby earthquakes?”
Tell an agent
Run a marine pre-operation check for my vessel at these coordinates.
Get a go or no-go verdict for my USV based on waves and wind.
POST /v1/robot-receipt Witness a robot decision as a black-box receipt · V1 Robot Receipt #
Ask an LLM
“Can I record a signed black-box receipt of what my robot was told when it acted?”
“Do I have to send raw sensor data to create a robot decision receipt?”
Tell an agent
Create a robot receipt for my drone's last decision from its hashed inputs.
Witness this embodied-AI decision as a signed black-box record.
GET /v1/robot-receipt/sample Get a sample robot decision receipt · V1 Robot Receipt Sample #
Ask an LLM
“What does a robot black-box receipt look like?”
“Is there a demo robot receipt I can verify in the browser?”
Tell an agent
Show me a sample robot receipt.
Get the demo robot-receipt/v1 for testing verification.
POST /v1/anchor Timestamp a snapshot hash with RFC 3161 · V1 Anchor #
Ask an LLM
“Can I get an independent RFC 3161 timestamp token proving a record existed at a time?”
“Can I timestamp just a SHA-256 digest instead of the whole snapshot?”
Tell an agent
Timestamp this snapshot's hash with an independent authority.
Anchor my SHA-256 digest with an RFC 3161 timestamp token.
POST /v1/anchor/upgrade Re-check a stored timestamp proof · V1 Anchor Upgrade #
Ask an LLM
“Can I re-check an old OpenTimestamps proof against its block attestation?”
“Do RFC 3161 timestamp tokens ever need upgrading?”
Tell an agent
Re-check my stored timestamp token.
Upgrade my legacy OpenTimestamps proof to its block attestation.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/dynamicfeed-ai:dynamicfeed-ai-robot-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

dynamicfeed-ai-robot-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Dynamic Feed — Live Data for AI Robot API
  description: Fresh, current data that AI models lack — 20 live domains, 94 read-only tools, over one REST API or a keyless MCP endpoint.
  contact:
    name: Dynamic Feed
    url: https://dynamicfeed.ai/
  version: 1.0.0
servers:
- url: https://dynamicfeed.ai
tags:
- name: Robot
paths:
  /v1/anchor/daily:
    get:
      tags:
      - Robot
      summary: V1 Anchor Daily
      description: 'L2 — the day''s world-state snapshot timestamped via RFC 3161 (one hash per day, free &

        batched via RFC 3161): a durable, tamper-evident record of what Dynamic Feed reported. Anchors

        on first call (idempotent), then returns the proof. ?date=YYYY-MM-DD; keyless.'
      operationId: v1_anchor_daily_v1_anchor_daily_get
      parameters:
      - name: date
        in: query
        required: false
        schema:
          type: string
          default: ''
          title: Date
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /v1/awareness:
    post:
      tags:
      - Robot
      summary: V1 Awareness
      description: 'Robot situational-awareness v1: ONE call returns a go / caution / no-go verdict plus the grounded

        facts behind it, for a robot (ground|humanoid|aerial|marine|orbital) at a location. NEVER blocks: the

        feeds fan out under a hard deadline and any laggard is dropped with the snapshot flagged `degraded`

        (fail-safe → the verdict can never be `go` when degraded, it floors to `caution`). Keyless in v1.


        Body: {"robot":{"id","class"},"location":{"lat","lon","alt_m"},"radius_km"?,"domains"?,

        "max_staleness_s"?,"limits"?,"deadline_ms"?,"require_signed"?}. Every response is signed with Ed25519

        (Rung B) · verify against GET /.well-known/keys. Timestamp a snapshot''s hash via POST /v1/anchor (Rung C).'
      operationId: v1_awareness_v1_awareness_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /v1/preflight:
    post:
      tags:
      - Robot
      summary: V1 Preflight
      description: 'Drone PRE-FLIGHT safety check: a preset over /v1/awareness for class=aerial. POST

        {"location":{"lat","lon","alt_m"?},"radius_km"?}. Returns a go / caution / no-go take-off verdict

        fused from wind & weather, air quality, space weather (GPS/comms integrity) and nearby hazards ·

        Ed25519-signed, hard-deadline (never hangs; degraded floors to caution). Keyless.'
      operationId: v1_preflight_v1_preflight_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /v1/road:
    post:
      tags:
      - Robot
      summary: V1 Road
      description: 'Ground / autonomous-vehicle OVER-THE-HORIZON hazard check: a preset over /v1/awareness for

        class=ground. POST {"location":{"lat","lon"},"radius_km"?}. Returns a go / caution / no-go verdict

        fused from weather, air quality and nearby earthquakes/hazards along the route · signed, never hangs.

        Keyless.'
      operationId: v1_road_v1_road_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /v1/humanoid:
    post:
      tags:
      - Robot
      summary: V1 Humanoid
      description: 'Humanoid PRE-OPERATION check: a preset over /v1/awareness for class=humanoid (a bipedal robot

        working AMONG PEOPLE). POST {"location":{"lat","lon"},"radius_km"?}. Returns a go / caution / no-go

        verdict fused from wind (topple risk, high centre of mass), precipitation (slip/footing), temperature

        (ice underfoot + actuator/battery envelope), air quality (tighter, people nearby) and nearby

        earthquakes · Ed25519-signed, hard-deadline (never hangs; degraded floors to caution).

        ADVISORY EVIDENCE ONLY: proof of what was true at a time, NOT a safety certification and NOT a

        guarantee it is safe to act; the robot''s own stack owns every action. Keyless.'
      operationId: v1_humanoid_v1_humanoid_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /v1/marine:
    post:
      tags:
      - Robot
      summary: V1 Marine
      description: 'Marine vessel / USV PRE-OPERATION check: a preset over /v1/awareness for class=marine. POST

        {"location":{"lat","lon"},"radius_km"?}. Returns a go / caution / no-go verdict fused from live

        significant WAVE HEIGHT (the primary driver), wind, a heavy-precipitation storm proxy, geomagnetic

        activity (GPS/comms) and nearby earthquakes (tsunami) · Ed25519-signed, hard-deadline (never hangs;

        degraded floors to caution). Inland points simply omit the sea-state factor. ADVISORY EVIDENCE only:

        not a safety certification and not a claim it is safe to sail; the vessel''s own stack owns every

        action. Keyless.'
      operationId: v1_marine_v1_marine_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /v1/robot-receipt:
    post:
      tags:
      - Robot
      summary: V1 Robot Receipt
      description: 'WITNESS a single robot / embodied-AI DECISION: the neutral ''black box'' receipt of what a robot

        was told and which model/policy decided, at the moment it acted. Ed25519-signed, transparency-logged,

        RFC 3161 timestampable. Privacy by CONSTRUCTION: the caller hashes the decision inputs (sensor/awareness

        context) LOCALLY and sends ONLY a fixed-length sha256 + non-PII labels. Body: {"robot_class":

        "ground|aerial|marine|orbital|humanoid", "model_id": "", "verdict":

        "go|caution|no-go", "inputs_sha256": ""} plus optional decision, awareness_ref (a prior

        /v1/awareness snapshot_id), region (COARSE, no precise coords), latency_ms, and a BYO-key co-signature.

        Auth: a FREE key (POST /signup). ADVISORY EVIDENCE ONLY: proves the decision record existed and is

        intact (tamper-EVIDENT, verifiable via /verify.js); it does NOT certify the action was safe/correct/

        lawful, is NOT a safety system, and is NOT the actuator (the robot''s own certified safety layer decides).

        Profile of receipt/v1. Anchor via POST /v1/anchor.'
      operationId: v1_robot_receipt_v1_robot_receipt_post
      parameters:
      - name: x-api-key
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Api-Key
      - name: x-rapidapi-proxy-secret
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Rapidapi-Proxy-Secret
      - name: x-rapidapi-user
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: X-Rapidapi-User
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /v1/robot-receipt/sample:
    get:
      tags:
      - Robot
      summary: V1 Robot Receipt Sample
      description: 'A keyless, signed SAMPLE robot-receipt/v1: the ''black box'' record of an embodied-AI decision (an

        aerial robot told CAUTION on degraded GPS, which held). Verify it in-browser via /verify.js, then flip

        a byte and watch verification fail. Advisory evidence only: not a safety system.'
      operationId: v1_robot_receipt_sample_v1_robot_receipt_sample_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /v1/anchor:
    post:
      tags:
      - Robot
      summary: V1 Anchor
      description: 'Timestamp a snapshot''s hash with an independent RFC 3161 authority — returns a signed timestamp

        token proving the record existed at time T, independently verifiable, even against us. Body:

        {"snapshot": {...}} (its canonical SHA-256 is timestamped) or {"digest_hex": ""}.

        Hashes ONLY, never data. Off the verdict hot path (Rung C).'
      operationId: v1_anchor_v1_anchor_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /v1/anchor/upgrade:
    post:
      tags:
      - Robot
      summary: V1 Anchor Upgrade
      description: 'Re-check a stored timestamp proof. RFC 3161 tokens are final at issue (nothing to upgrade); a

        legacy OpenTimestamps proof is folded into its block attestation. Body: {"token_b64": "..."}

        (legacy {"proof_ots_b64": "..."} still accepted).'
      operationId: v1_anchor_upgrade_v1_anchor_upgrade_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError