--- title: "Heap Page product signals" description: "Collect the public discussion Heap Page shows beside a product. The collector reads its own free sources, keeps only the records that anchor to the product, and stores them on heap.page, where the product page serves the" --- > Documentation Index > Fetch the complete documentation index at: https://help.tooluse.net/llms.txt > Use this file to discover all available pages before exploring further. # Heap Page product signals

Collect the public discussion Heap Page shows beside a product. The collector reads its own free sources, keeps only the records that anchor to the product, and stores them on heap.page, where the product page serves them.

What you can do (5)

What you can do

Available commands: 5 (2 read, 3 write). Enable only the commands your application needs.

Command Effect
Buy the next paid discussion batch — heap-page.signals.paid.dispatch Write
Store what a paid batch returned — heap-page.signals.paid.collect Write
Collect the next product-signal batch — heap-page.signals.collect Write
Read collection coverage — heap-page.signals.coverage.read Read
Read one product's collected mentions — heap-page.signals.mentions.read Read

Connect and use

Connect and use

Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.

Get your provider credentials

Follow these steps for Heap Page product signals, then enter the issued values in the connection form below.

  1. Ask the Heap Page product signals service administrator for connection credentials and the account or endpoint identifiers required by this integration.

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Heap Page collector token Required
Heap Page API origin Optional

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

Buy the next paid discussion batch — heap-page.signals.paid.dispatch

Run Buy the next paid discussion batch with Heap Page product signals. This command can change provider data. Review the target and input before invoking it.

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
limit integer Optional Products this batch minimum: 1; maximum: 20

Full JSON Schema

Full JSON Schema

Example input

{
  "limit": 10
}

At most 1 provider requests per invocation; timeout: 120 seconds.

Store what a paid batch returned — heap-page.signals.paid.collect

Run Store what a paid batch returned with Heap Page product signals. This command can change provider data. Review the target and input before invoking it.

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
snapshotId string Optional Provider snapshot minLength: 1; maxLength: 120; pattern: "^[A-Za-z0-9_-]{1,120}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "snapshotId": "s_m1fixture2345"
}

At most 1 provider requests per invocation; timeout: 300 seconds.

Collect the next product-signal batch — heap-page.signals.collect

Run Collect the next product-signal batch with Heap Page product signals. This command can change provider data. Review the target and input before invoking it.

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
limit integer Optional Products this run minimum: 1; maximum: 60
maxProviderRequests integer Optional Source requests this run minimum: 2; maximum: 120

Full JSON Schema

Full JSON Schema

Example input

{
  "limit": 25,
  "maxProviderRequests": 50
}

At most 1 provider requests per invocation; timeout: 300 seconds.

Read collection coverage — heap-page.signals.coverage.read

Run Read collection coverage with Heap Page product signals. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

This tool has no input parameters.

Full JSON Schema

Full JSON Schema

Example input

{}

At most 1 provider requests per invocation; timeout: 30 seconds.

Read one product's collected mentions — heap-page.signals.mentions.read

Run Read one product's collected mentions with Heap Page product signals. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
slug string Required Product slug minLength: 1; maxLength: 2000; pattern: "^[a-z0-9][a-z0-9-]{0,79}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "slug": "1password"
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Source: https://help.tooluse.net/integrations/heap-page/index.mdx