# Customer Proof — Which named customer stories does this vendor publish?

Named customer stories linked from the vendor's official website.

- Capability id: `customer.evidence`
- Actor: `impressionable_lupine/verified-customer-proof` (ID `kRk9vTOnhmGMMrMCg`), default build `0.2.3`
- Apify Store: https://apify.com/impressionable_lupine/verified-customer-proof
- Page: https://agents.retainly.dev/capabilities/customer-proof
- Last metadata check: 2026-10-08T12:16:53.713706+00:00 (read-only; not live status)

## Workflow

Find case-study evidence for vendor qualification and account research.

Simpler alternative: If you only need a vendor’s customers page URL, open it directly. Choose this for dated named-story rows with per-row evidence.

Do not choose for:
- Independent endorsement verification
- Proving an ongoing customer relationship
- Treating unlinked logo walls as verified case studies

## Input

| Field | Required | Constraints | Description |
|---|---|---|---|
| `company_website` | yes | required, string, max 2048 chars | One public, official company domain or HTTPS URL. The Actor follows same-company customer stories only. |
| `max_customers` | no | optional, integer 1–6, default 5 | Return at most this many verified story rows. Unverifiable links do not consume this limit; all checks remain within the request and time budget. The result is not exhaustive. |

Minimal valid input:

```json
{
  "company_website": "https://linear.app/"
}
```

Input schema: https://agents.retainly.dev/schemas/customer-proof/input_schema.json
Report schema: https://agents.retainly.dev/schemas/customer-proof/report.schema.json

## Price and charge trigger

- Model: PAY_PER_EVENT, event `verified-customer-report` (“Verified customer proof report”), $0.02 USD, max 1 event per run.
- Store event description (verbatim): “One source-checked report with public customer evidence. Unknown or invalid results are free.”
- Charge trigger: One event for a positive report, which may be a partial list.
- No event when: unknown and invalid_input produce no event.
- Standard Actor platform usage included under the configuration checked on 8 Oct 2026; recheck before purchase.
- Caps are not discounts and do not guarantee a positive result. Unknown/invalid checks produce no eligible report event; caller model/workflow costs are separate.

## Statuses

| Status | Meaning | Eligible report event |
|---|---|---|
| `verified_customer_proof` | Named customers and stories verified on vendor-linked first-party pages. May be a partial list. | yes |
| `unknown` | No named customer story could be verified in the checked sources. | no |
| `invalid_input` | Fix the caller input. | no |

## Evidence and limits

- Verification scope: Named customers and stories verified on vendor-linked first-party case-study pages.
- Coverage limits: These are vendor-published claims, not independent endorsements or proof the relationship is current. Generic logo walls alone are insufficient.
- Request bounds: 12 requests, 10 MB total, 3 MB per page, 45-second network budget.

## Recorded example

Recorded example — observed 2026-10-08 11:46 UTC · owner-funded release test · not an independent purchase.
Subject: Linear. Run `6ug7OjCIYmqvfcBJd`, build 0.2.3. Reports may precede final event charging; their billing fields alone do not establish a settled debit.
Full report with provenance: https://agents.retainly.dev/examples/customer-proof.json

Input used:

```json
{
  "company_website": "https://linear.app/"
}
```

## Call it (after the caller authorizes spending)

Connecting does not authorize spending. Inspecting metadata never starts a run.

Inspect without purchase (MCP, anonymous endpoint `https://mcp.apify.com?tools=search-actors,fetch-actor-details`):

```json
{
  "name": "fetch-actor-details",
  "arguments": {
    "actor": "impressionable_lupine/verified-customer-proof",
    "output": {
      "pricing": true,
      "inputSchema": true,
      "outputSchema": true,
      "metadata": true,
      "readme": true
    }
  }
}
```

Inspect without purchase (REST, no token):

```bash
# Free, read-only: public Actor metadata (pricing, builds). Does not start a run.
curl "https://api.apify.com/v2/acts/kRk9vTOnhmGMMrMCg"
```

MCP `call-actor` (endpoint `https://mcp.apify.com?tools=actors,runs,storage`; run limits live in `callOptions`, never in `input`):

```json
{
  "name": "call-actor",
  "arguments": {
    "actor": "impressionable_lupine/verified-customer-proof",
    "input": {
      "company_website": "https://linear.app/"
    },
    "waitSecs": 30,
    "callOptions": {
      "build": "0.2.3",
      "memory": 512,
      "timeout": 60,
      "maxTotalChargeUsd": 0.02
    }
  }
}
```

MCP follow-ups (same run):

```json
{
  "name": "get-actor-run",
  "arguments": {
    "runId": "<runId returned by call-actor>"
  }
}
```

```json
{
  "name": "get-dataset-items",
  "arguments": {
    "datasetId": "<datasetId returned by call-actor>",
    "clean": true
  }
}
```

REST API v2:

```bash
# Paid run in YOUR Apify account. Only after spending is authorized.
# Set APIFY_TOKEN securely in your client/shell; never paste it into URLs or shared files.
curl -X POST "https://api.apify.com/v2/acts/kRk9vTOnhmGMMrMCg/runs?build=0.2.3&memory=512&timeout=60&maxTotalChargeUsd=0.02&waitForFinish=30" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"company_website":"https://linear.app/"}'
```

```bash
# Save data.id (run ID) from the first response. On timeout/ambiguity, poll THIS run.
# Never start a second charged run to recover output.
curl "https://api.apify.com/v2/actor-runs/$RUN_ID" \
  -H "Authorization: Bearer $APIFY_TOKEN"
```

```bash
# data.defaultDatasetId from the run object (one report item).
curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?format=json&clean=true" \
  -H "Authorization: Bearer $APIFY_TOKEN"
```

Recovery rule: Save the run ID from the first response; on timeout or ambiguous response, poll that same run; never start a second charged run to recover output.