Documentation

How to use the scanner, connect Make.com and n8n, and add Proofled as a Claude Cowork connector.

Documentation

How to use the scanner, connect Make.com and n8n, and add Proofled as a Claude Cowork custom connector.

Full markdown guide in the repo: context/docs/USER-GUIDE.md

1. Website scanner
  1. Open https://proofled.sheessaleemllc.com/
  2. Type a website address (example: shopify.com)
  3. Click Scan — you get the stack, sales gaps, and Connect (LinkedIn, Instagram, X, email, phone)
  4. Or use Many websites and download CSV (includes Connect columns)

No login needed for the browser scanner.

2. Accounts, approval & API keys (simple English)

What is an API key? A special password for apps (Make, n8n, Claude) — not for humans clicking around the website.

How it works while you are not fully commercial:

  1. Someone signs up on your site
  2. They wait as Pending — they cannot create keys yet
  3. You open Admin and click Approve
  4. They open API keys → Create API key → copy it
  5. They paste that key into Make / n8n / Claude

You stay in control. No random person can burn your free usage without your OK.

One-time setup (owner)

  1. Create free DB: neon.tech
  2. In Neon SQL Editor, run the SQL file from GitHub: scripts/setup-db.sql
  3. In your hosting environment variables set DATABASE_URL, AUTH_SECRET, and STACKSIGNAL_ADMIN_EMAIL=your@email.com
  4. Redeploy, then sign up with that admin email

API access uses dashboard keys (after approval) or your STACKSIGNAL_API_KEY env var — there is no shared bootstrap key.

3. Claude Cowork — add Proofled as a connector

Proofled runs a remote MCP server Claude can call directly.

Connector URL (copy this)

https://proofled.sheessaleemllc.com/mcp?api_key=YOUR_API_KEY

After you set your own STACKSIGNAL_API_KEY, replace the key in the URL.

Steps in Claude

  1. Open Claude (Cowork or claude.ai)
  2. Go to Customize → Connectors
    (Team plans: Organization settings → Connectors)
  3. Click + or Add Add custom connector (or Custom → Web)
  4. Name: Proofled
  5. Remote MCP server URL: paste the connector URL above
  6. Leave OAuth Client ID / Secret empty (not required)
  7. Save, then enable Proofled in Cowork
  8. Ask Claude something like:
    “Scan https://cloudnixia.vercel.app, list their tech stack, sales gaps, and LinkedIn or email so I can outreach.”

Tools Claude gets

  • scan_website — technology list + opportunity score + Connect links
  • find_connect — LinkedIn, Instagram, X, email, and phone for outreach
  • analyze_gaps — missing analytics, CRM, chat, etc. (includes Connect)
  • bulk_scan — several sites at once (plan max: Starter 500 / Growth 1,500 / Scale 3,000)
  • draft_pitch — grounded cold email / LinkedIn DM from scan evidence
  • list_signals — active Why-Now change signals for monitored accounts
  • list_capabilities — what Proofled can do

If it doesn’t connect

  1. Wait for the latest deployment to finish
  2. Open https://proofled.sheessaleemllc.com/mcp — you should see JSON (not an error page)
  3. Double-check the api_key in the URL
  4. Reload Claude and try adding the connector again
4. Make.com & n8n

Use HTTP modules against the REST API. Full steps: API & Connectors

POST https://proofled.sheessaleemllc.com/api/v1/scan
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{"url":"https://example.com"}
5. REST API reference
EndpointAuthPurpose
GET /api/v1/healthNoHealth check
POST /api/v1/scanYesScan one URL
POST /api/v1/bulkYesScan up to 50 URLs
GET /api/v1/openapiNoOpenAPI document
POST /mcpYesClaude / MCP tools (includes draft_pitch)
GET/POST /api/pitchLogin sessionAI pitch writer (bring-your-own API key). Body may include provider + model. Requires a key under Settings → AI / Pitch. Returns 400 byok_required if missing; 503 pitch_disabled when Admin turns it off.

Scoring fields: use leadScore (0–100, higher = more to sell into) for outreach ranking. opportunity is deprecated — its score now mirrors leadScore.score for older clients. Prefer audit.issues + gaps for the underlying findings.

Pitch body (POST /api/pitch): { findings | url, provider?, model?, tone?, agency?: { agencyName, senderName, services } }. Uses your OpenRouter / OpenAI / Anthropic / xAI key only — never a shared Proofled server key. Never invents a sender name — omit senderName to sign as [Your name].

6. Detection accuracy

Only technical proof counts: scripts, headers, cookies, platform files. Marketing text is ignored so you don’t get false matches like “WordPress” from a service description.