Developers / agents

Agent-native access

Discover publicly. Authenticate only when the requested capability requires it.

Dynamik publishes a safe public catalog separately from account-scoped tools. Every dataset record states freshness, provenance, limitations, and access status so an agent can explain what it can use before asking a person to connect anything.

Open discovery document
No account

Public catalog

Read dataset identity, release freshness, coverage, limitations, provenance URLs, and declared access tiers.

https://api.dynamikorbits.com/v1/public/catalog
No account

Public MCP

Search and describe public dataset metadata and obtain bounded sample-request links. No account or workspace data is exposed.

  • search_datasets
  • describe_dataset
  • get_dataset_sample_link
https://api.dynamikorbits.com/public/mcp
Account credential

Cloud MCP

Use account-scoped tools such as News Tracker. Tools are filtered by the scopes and organization bound to the credential.

https://api.dynamikorbits.com/mcp

Anonymous flow

Start with useful public evidence.

  1. 1. Read the public catalog or connect the public MCP endpoint.
  2. 2. Search or describe a dataset and inspect its declared release metadata.
  3. 3. Request a bounded sample link when the dataset publishes one.
  4. 4. Cite the canonical dataset page, version, manifest, and limitations.

Account flow

Connect protected capabilities explicitly.

The current Cloud MCP uses a named, revocable, read-only credential. Account creation, credential minting, and future paid upgrades always require explicit user action; anonymous tools cannot provision compute or inspect entitlements.

Connect your agent