Intel Report
by Bytemine in Company & people data
Analyze a company's highest value pages such as about, team, contact, pricing, careers, and case studies, and return one intelligence report: company profile, contacts, social profiles, tech stack, sales signals, pain points, and personalized conversation starters. Billed per page analyzed with a 5 page minimum.
POST https://agents.bytemine.ai/zcj/vwjn1xt3gg67/functions/v1/api-gateway/company/intel/report
Last 30 days
Status and outage history · Atom feed
- Uptime
- 90.0%
- Response time
- 1.8 s typical, 3.6 s slowest 5%
- Last check
- 4 h ago
- Next check
- any minute now
How to call it
POST https://agents.bytemine.ai/zcj/vwjn1xt3gg67/functions/v1/api-gateway/company/intel/report
Each call costs $0.05 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://agents.bytemine.ai/zcj/vwjn1xt3gg67/functions/v1/api-gateway/company/intel/report
content-type: application/json
{
"url": "example"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Company URL to report on. |
Example response
The listing has no example response.
Call it from code
The curl command shows the payment challenge.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://agents.bytemine.ai/zcj/vwjn1xt3gg67/functions/v1/api-gateway/company/intel/report' \
-H 'content-type: application/json' \
--data-raw '{"url":"example"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://agents.bytemine.ai/zcj/vwjn1xt3gg67/functions/v1/api-gateway/company/intel/report' \
-H 'content-type: application/json' \
--data-raw '{"url":"example"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeWe don't show code that pays this service: it uses a payment scheme other than exact, which needs a different client setup.
Security scan
- Payment address changed recently in payment
Payment address changed from 0xa6de0cb73d5b9a8a6c3c3862aba0ad32fb875387 to 0xc655951016d69b6ac50b018d72b89130e322e113
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Passed | 402 | 2.3 s | $0.05 |
| 8 h ago | Passed | 402 | 1.8 s | $0.05 |
| 12 h ago | Passed | 402 | 6.9 s | $0.05 |
| 15 h ago | Expected HTTP 402, got 504 | 504 | 5.6 s | - |
| 19 h ago | Passed | 402 | 1.8 s | $0.05 |
| 23 h ago | Passed | 402 | 1.6 s | $0.05 |
| 27 h ago | Passed | 402 | 2.5 s | $0.05 |
| 31 h ago | Passed | 402 | 1.3 s | $0.05 |
| 34 h ago | Passed | 402 | 1.8 s | $0.05 |
| 38 h ago | Passed | 402 | 2.7 s | $0.05 |
| 41 h ago | Passed | 402 | 3.6 s | $0.05 |
| 45 h ago | Passed | 402 | 2.1 s | $0.05 |
| 2 days ago | Passed | 402 | 1.6 s | $0.05 |
| 2 days ago | Passed | 402 | 2.3 s | $0.05 |
| 2 days ago | Timed out | - | - | - |
History
| 14 Oct 2026 | Payment address changed from 0xa6de0cb73d5b9a8a6c3c3862aba0ad32fb875387 to 0xc655951016d69b6ac50b018d72b89130e322e113 |
| 14 Oct 2026 | Payment address changed from 0x72476ed52529c08def4112e3253e8e960fc12074 to 0xa6de0cb73d5b9a8a6c3c3862aba0ad32fb875387 |
| 14 Oct 2026 | Payment address changed from 0x8896a2898e2fee38943d0a33e96143aea6f81eb5 to 0x72476ed52529c08def4112e3253e8e960fc12074 |
| 14 Oct 2026 | Payment address changed from 0x78ebf2b391b61e059757c6978a8dd326fc88a9b9 to 0x8896a2898e2fee38943d0a33e96143aea6f81eb5 |
| 13 Oct 2026 | Payment address changed from 0xea97f5a6504add9854b059b450f8dbe9c4ad22d1 to 0x78ebf2b391b61e059757c6978a8dd326fc88a9b9 |
| 13 Oct 2026 | Payment address changed from 0xc4263b03c6b25b359ca032d4be29358e49337519 to 0xea97f5a6504add9854b059b450f8dbe9c4ad22d1 |
| 13 Oct 2026 | Payment address changed from 0x8afce9a33e7a4944bc537542d421ce31d94a81c4 to 0xc4263b03c6b25b359ca032d4be29358e49337519 |
| 13 Oct 2026 | Payment address changed from 0xc0f384d35971e72b220644e870fc7e6d784be9d4 to 0x8afce9a33e7a4944bc537542d421ce31d94a81c4 |
| 13 Oct 2026 | Payment address changed from 0xd439dc226792438d979fd2913052e6a796289ad5 to 0xc0f384d35971e72b220644e870fc7e6d784be9d4 |
| 13 Oct 2026 | Payment address changed from 0x6e792e261977bbf5ed3d81d0760430f62f37a408 to 0xd439dc226792438d979fd2913052e6a796289ad5 |
| 12 Oct 2026 | Payment address changed from 0x0b16126878cef8a854ee72be7be3660ea2d50951 to 0x6e792e261977bbf5ed3d81d0760430f62f37a408 |
| 12 Oct 2026 | Payment address changed from 0x9245660c5c17203c71a5ad38ab79b692630022a4 to 0x0b16126878cef8a854ee72be7be3660ea2d50951 |
| 12 Oct 2026 | Payment address changed from 0x6ff0201a3fff140cfc6fb7fee3bf420009c08e6e to 0x9245660c5c17203c71a5ad38ab79b692630022a4 |
| 12 Oct 2026 | Payment address changed from 0x0483615adaac28452b7df67eb1611f120a8fc6fa to 0x6ff0201a3fff140cfc6fb7fee3bf420009c08e6e |
| 12 Oct 2026 | Payment address changed from 0xe0c48f787f76bf43ce9bb70b19d1c3d51f723d6a to 0x0483615adaac28452b7df67eb1611f120a8fc6fa |