BUILDER STARTER PATH

Build with verified Malaysian data.

Before your workflow uses a public dataset, inspect its source identity, freshness, licence and reuse context, structural signals, and recorded limitations. DataPulse helps you make that evidence-qualified decision while the official publisher remains the source of record.

Start small: verify a dataset, fetch from its canonical surface, then keep the evidence boundary in your answer.

VERIFY → FETCH → BUILD

A three-step path to a first evidence-aware workflow.

Each step leaves you with something reviewable instead of an unqualified answer.

01 / VERIFY

Inspect the dataset report.

Open the report for its source, freshness, licence, structural evidence, and limitations before deciding it fits your use case.

Open the fuelprice report

02 / FETCH

Use the canonical data surface.

Fetch from the official source named in the report, or use DataPulse’s read-only MCP surface to retrieve published context.

Inspect one official fuelprice record

03 / BUILD

Preserve the evidence boundary.

Make a small retrieval or agent workflow that states the dataset, observed signals, and limitations alongside the answer it supports.

Follow the notebook workflow

THE NOTEBOOK

Your first successful outcome: a guarded official-data fetch.

The 12-cell notebook walks through checking health, inspecting evidence, deciding whether to use a dataset, and then fetching official data. After opening it, a beginner should be able to see why a workflow proceeds or stops, rather than treating a successful request as proof that the data is suitable.

MCP QUICKSTART

Connect to published context with a read-only endpoint.

This is a starter configuration for clients that use an mcpServers URL shape; client configuration varies. The endpoint provides read-only DataPulse context, not upstream writes or a browser session.

{
  "mcpServers": {
    "datapulse-my": {
      "url": "https://mcp.data-pulse.my/mcp"
    }
  }
}
Read the MCP reference and tool schemas

WORKED EXAMPLE / FUELPRICE

Use only what the evidence supports.

Start with the weekly fuel-price dataset, then let its current report determine the scope of your use.

  1. Find the fuelprice dataset report.
  2. Inspect its source, freshness, licence, structural notes, and limitations.
  3. Fetch from the official data.gov.my surface only if that evidence fits the task.

CLAIM BOUNDARY

What not to claim

Do not describe the result as universally current, complete, or fit for every purpose. State the report’s observed evidence and limitations, and defer to the official source for the record itself.