Skip to main content
This tutorial is for users who want to use data capabilities directly in the Data Hub web portal. You do not need to configure MCP or write code. Choose a suitable Data App, fill in the parameters, and check the results on the page.

General connection

Do not pick an app first. Connect the Data Hub MCP, then let the agent search for and run the right capability.

Codex: connect a specific app

When you already know the app, add that capability to Codex as a fixed tool.

Claude Code: connect a specific app

When you already know the app, add that capability to Claude Code as a fixed MCP server.

​
Before you start

Have an Octoparse account you can sign in to, and a data target you want to query, such as a keyword, a content URL, a product ID, or a platform filter. For a first trial, start with a small set of parameters and confirm the fields, freshness, and billing match your expectations.

​
Open and sign in to Data Hub

1

Open Octoparse Data Hub

Go to the Octoparse Data Hub. Use search and category filters to find the data capability you need. Apps, categories, and prices change continuously, so rely on what the page shows right now.
2

Sign in to your Octoparse account

Click the account entry in the top-right corner and sign in. You need to be signed in to submit an online run, view results, and export the data files the page supports.

​
Choose and understand a Data App

1

Pick a suitable Data App

Click the Data App that matches your scenario. The app name only helps with a first pass. Whether it fits should be judged by the data description, input parameters, and output fields on the detail page.
2

Check the scope and cost

Read the Overview, Input, Output, Integration, and Pricing sections in turn. Confirm the data source and freshness, required parameters, returned fields, per-call limits, and billing unit before you scale up the data volume.

​
Run online and check the results

1

Fill in parameters and submit a run

Click Try It Now and fill in the form. Fields marked with an asterisk are required. List, paging, and quantity parameters must follow the format and limits shown on the page. Validate with a small amount of data the first time.
2

Check the returned data

After the run completes, view the results as a table or JSON on the page. Check the status, record count, and core fields first. Once the results look right, use the export options the page supports or connect the app to a downstream workflow.
A successful online run only proves that the current parameters return results. Before production use, validate edge cases, data completeness, and real cost with parameters that are close to your actual scenario.

​
Checklist

  • You signed in to Data Hub and found the target Data App.
  • You checked the input parameters, output fields, and public price.
  • You completed one online run with a small set of parameters.
  • You checked the status, record count, and key fields.

​
Next: connect an agent

If you have not decided on an app, choose the general connection. If you already have a fixed app, follow the Codex or Claude Code tutorial for your client.

General connection

Connect once, then let the agent search, compare, and run Data Apps.

Codex: specific app

Pick the app first, then configure Codex and complete the first call.

Claude Code: specific app

Pick the app first, then add and verify the MCP server in Claude Code.