Extract Facts From a Public Webpage

Ask for a short list of facts and receive only source-backed matches.

This is the simpler alternative to defining a full output schema. Give the Actor one page plus fact names such as title, price, availability, or date. It reports what the static page supports and identifies what is missing; it does not fill gaps by guessing.

This Actor is self-service. Normal runs return one structured dataset item; handled failures return one safe failure item without requiring a Dravara account, operator, or support fulfillment.

Pricing and charge controls

The live Apify Store pricing section is authoritative. This Pay per event + usage product can charge the customer for (1) one Dravara apify-actor-start event per Actor run, (2) one Dravara product result event only after a chargeable success, and (3) customer-paid Apify platform usage. The underlying Apify platform usage remains separate. Dravara does not reduce its event charge to absorb the underlying Apify platform usage. Before running, set Apify's maxTotalChargeUsd option to a limit you accept.

The custom result event is charged only for a success result. Approved partial and failed paths do not create that custom event. Each Actor run can still record the separate one-time apify-actor-start creator event, and the underlying Apify platform usage can still apply. The apify-default-dataset-item event is configured at $0 for this release.

Input

{
  "url": "https://example.com/product",
  "facts": ["title", "price", "availability"],
  "include_evidence": true,
  "idempotency_key": "550e8400-e29b-41d4-a716-446655440000"
}

facts accepts 1-20 unique, non-blank requests. Short field-like names work best because this version uses deterministic aliases and labeled page content, not open-ended model inference. The URL is limited to 4,096 characters, and each fact request is limited to 500 characters. include_evidence remains accepted for compatibility, but evidence can no longer be disabled: both true and false return it.

idempotency_key is optional. It accepts 1-128 ASCII letters, digits, periods, underscores, tildes, or hyphens. Dravara HMAC-scopes it to the authenticated Apify customer and this product. While the replay record remains retained, reusing the same key with the same canonical input can return the exact durable result in a later Actor run; reusing it with changed input is rejected. Other customers and products have separate namespaces. A confirmed terminal replay does not create another Dravara result event or result artifact, but the new Actor run can still incur its separate Actor-start event and Apify platform usage. Dravara does not store or return the raw key. Use a unique opaque job ID, such as a UUID—not a secret or personal identifier.

Use cases

• Collect a product title, displayed price, and availability from one public page.
• Pull dates, descriptions, or canonical links into an agent workflow without a schema.
• Check whether a page exposes a short list of named facts and preserve matching excerpts.

Output and evidence

The default dataset receives one status-bearing item. Each extracted fact has the original request, a scalar value, mandatory non-empty normalized bounded evidence, a deterministic source-agreement indicator in the confidence field, and a contradictions list. That indicator is not an accuracy probability. The result also includes missing_facts, retrieval provenance, bounded usage telemetry, warnings, safe structured errors, and cost telemetry. success means all requested facts were found; partial means some verified facts were found; failed means none were found or the page could not be fetched.

An Apify run can complete while this item has status: failed. Integrations must inspect the dataset item's status and errors, not the Actor run status alone.

Failures and retries

Read the dataset item's status, errors, and each error's retryable value. The same idempotency key and canonical input replay the same terminal failure; changed input with that key is rejected. Inspect the original dataset and Charged events before starting another run. Correct nonretryable input first. For a retryable fetch or capacity failure, wait for recovery and use a new unique key only when billing is clear. That new run can incur its Actor-start event, Apify platform usage, and a result event after a chargeable success.

If the Actor itself fails after a dataset item appears, do not start another run yet. Compare that run's default dataset with its Charged events first.

Evidence includes a whitespace-normalized source excerpt bounded to 4,000 characters, a selector when available, and the source URL. The excerpt is not a byte-for-byte HTML quote: whitespace is normalized, and long elements are truncated to that limit. A source-backed value is not an independent endorsement of the publisher's claim.

Complete output example

Actual identifiers, timestamps, timing, and page values vary.

{
  "run_id": "d6cb91ab-7c0c-4074-9277-e4477ba7f304",
  "status": "success",
  "next_action": null,
  "warnings": [
    "This result does not include the final Apify platform-usage amount. Check this run's Usage and Charged events for final billing.",
    "Evidence excerpts normalize whitespace and are bounded to 4,000 characters; use the returned source URL for verbatim review."
  ],
  "errors": [],
  "retrieval": {
    "requested_url": "https://example.com/product",
    "final_url": "https://example.com/product",
    "retrieved_at": "2026-07-27T12:00:00Z",
    "method": "static_https",
    "http_status": 200,
    "redirect_count": 0,
    "content_type": "text/html",
    "bytes_received": 286
  },
  "usage": {
    "duration_ms": 16,
    "bytes_processed": 286,
    "extraction_attempts": 3
  },
  "cost": {
    "currency": "USD",
    "total_cost_usd": null,
    "billable_events": []
  },
  "url": "https://example.com/product",
  "facts": [
    {
      "requested_fact": "title",
      "value": "Starter plan",
      "evidence": [{
        "text": "Starter plan",
        "selector": "script[type=\"application/ld+json\"]",
        "source_url": "https://example.com/product"
      }],
      "confidence": 1.0,
      "contradictions": []
    },
    {
      "requested_fact": "price",
      "value": 12,
      "evidence": [{
        "text": "12",
        "selector": "script[type=\"application/ld+json\"]",
        "source_url": "https://example.com/product"
      }],
      "confidence": 1.0,
      "contradictions": []
    },
    {
      "requested_fact": "availability",
      "value": true,
      "evidence": [{
        "text": "In stock",
        "selector": "script[type=\"application/ld+json\"]",
        "source_url": "https://example.com/product"
      }],
      "confidence": 1.0,
      "contradictions": []
    }
  ],
  "missing_facts": []
}

Expected runtime

A responsive static page usually finishes in seconds. Remote-server speed and shared capacity can vary. One fetch uses an 8-second connect timeout and a 12-second read timeout; the Actor has a five-minute default run timeout.

Durable replay and retention

Paid launch fails closed unless Dravara's durable result store is enabled. For a paid run, the validated result JSON is stored as a compressed canonical response envelope in a private R2 bucket and becomes eligible for deletion after 365 days. PostgreSQL stores bounded run, settlement, artifact-reference, quota, retention-claim, cost/revenue, and replay-identity metadata; it does not store the full fetched page or raw request body. This persistence supports exact result replay; it is not page monitoring. When supplied, idempotency_key is stored by Dravara only through the namespaced HMAC replay identity and the request digest, not as raw text.

Apify separately retains normal run input and dataset output under the runner's storage settings. Deleting that Apify storage does not itself delete Dravara's durable records. After a terminal run is at least 365 days old, Dravara's retention worker can irreversibly minimize its platform identity, replay identity, input digest, and free-form run metadata only when its artifacts have been deleted, reconciliation is final, and no hold or failed retention claim remains. Run status, timestamps, result-integrity hash, economic records, and settlement evidence remain under a separate accounting and dispute-retention policy; not all PostgreSQL data expires after 365 days. Customer-key replay is no longer available after those replay identities and result artifacts are minimized. See Dravara Privacy for the complete boundary.

Version 1 limits

• URL input is static public HTTPS only, on port 443.
• A fetched page is limited to 2 MB of decoded HTML and up to three redirects; every redirect destination is revalidated.
• There is no login support, JavaScript execution, browser rendering, proxy support, CAPTCHA bypass, access-control bypass, or form submission.
• One page is processed per run. There is no crawl, screenshot capture, semantic question answering, model-based guessing, or private-page access.
• There is no product-level monitoring, scheduling, or webhook delivery.

Do not put passwords, session tokens, API keys, or private customer data in a URL or idempotency_key. Credentials and URL fragments are rejected. Page content is processed by Dravara, LLC's private gateway using deterministic extraction rules. The destination site receives a request from that gateway and may retain it under the site's own logging and privacy practices.

Support: support@dravarahq.com