# Integration Evidence — Does this vendor officially document a named integration?

Official evidence for a supplied integration name.

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

## Workflow

Check a precise integration claim before recommending a vendor.

Simpler alternative: If the vendor publishes an integrations directory or marketplace API you already query, use it directly. Choose this to check one precise integration claim with dated evidence.

Do not choose for:
- Testing a live software connection
- Proving account or plan entitlement
- Checking arbitrary free-text claims

## Input

| Field | Required | Constraints | Description |
|---|---|---|---|
| `company_website` | yes | required, string, max 2048 chars | One public official HTTPS company website; the Actor follows only linked same-company integration pages. |
| `integration_name` | yes | required, string, max 80 chars | One exact software or app name to check, such as GitHub or Salesforce. |

Minimal valid input:

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

Input schema: https://agents.retainly.dev/schemas/integration-evidence/input_schema.json
Report schema: https://agents.retainly.dev/schemas/integration-evidence/report.schema.json

## Price and charge trigger

- Model: PAY_PER_EVENT, event `verified-integration-report` (“Verified report”), $0.02 USD, max 1 event per run.
- Store event description (verbatim): “One source-checked report with verified evidence. Unknown or invalid results are free.”
- Charge trigger: One event when the status is verified_integration.
- No event when: Missing, ambiguous, negated or blocked documentation is unknown and produces no event; unknown is not proof of no integration. invalid_input produces 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_integration` | Official linked documentation explicitly identifies the requested integration. A working connection was not tested. | yes |
| `unknown` | Documentation missing, ambiguous, negated or blocked. Not proof of no integration. | no |
| `invalid_input` | Fix the caller input (integration_name is required, at most 80 characters). | no |

## Evidence and limits

- Verification scope: Official linked documentation explicitly identifies the requested integration.
- Coverage limits: Documentation does not establish a working connection, authentication, plan entitlement or current endpoint behavior.
- Request bounds: 8 requests, 7 MB total, 3 MB per page, 35-second network budget.

## Recorded example

Recorded example — observed 2026-10-08 11:47 UTC · owner-funded release test · not an independent purchase.
Subject: Linear + GitHub. Run `uvTsKHhC3kz3nT9qd`, build 0.2.4. 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/integration-evidence.json

Input used:

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

## 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-integration-evidence",
    "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/VNySEt559gcOuwjE9"
```

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-integration-evidence",
    "input": {
      "company_website": "https://linear.app/",
      "integration_name": "GitHub"
    },
    "waitSecs": 30,
    "callOptions": {
      "build": "0.2.4",
      "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/VNySEt559gcOuwjE9/runs?build=0.2.4&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/","integration_name":"GitHub"}'
```

```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.