Search1API Trending
Get current trending topics from developer communities such as GitHub trending repositories and Hacker News front page. Send a POST with a JSON body containing search_service and optional max_results. Returns ranked items with title, URL and summary. Suited to newsletters, developer-tool market research and agents tracking what is popular today.
- Selected price
- $0.001 / callPublished pricing
- Providers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Provider | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
search1apiCurrent Search1API Trending · POST | $0.001 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
No response structure is available yet. Run a request to inspect its response.
No response structure is available yet. Run a request to inspect its response.
- Method
- POST
- Endpoint
https://api.openany.si/v1/agent-apis/search1api/trending- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
Generated request template. Review placeholder values and input constraints before use.
curl \
'https://api.openany.si/v1/agent-apis/search1api/trending' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"search_service": "<search_service>"
}'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
search_service | JSON request bodybody | string | Yes | Source of trends: github or hackernews. |
max_results | JSON request bodybody | integer | No | Number of items to return. |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
No response example is configured. A real response is available only after running the API, or when a published sample is added.
Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# Search1API Trending
Get current trending topics from developer communities such as GitHub trending repositories and Hacker News front page. Send a POST with a JSON body containing search_service and optional max_results. Returns ranked items with title, URL and summary. Suited to newsletters, developer-tool market research and agents tracking what is popular today.
Documentation: https://openany.si/apis/e9c33335-d241-424d-be1f-ad963cd094a2
Method: POST
Endpoint: https://api.openany.si/v1/agent-apis/search1api/trending
Price: $0.001 / call
Provider: search1api
Contract revision: 3
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Generated request template — review values before use
```bash
curl \
'https://api.openany.si/v1/agent-apis/search1api/trending' \
-X POST \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"search_service": "<search_service>"
}'
```
## API contract
```json
{
"resource_type": "api",
"name": "Search1API Trending",
"endpoint": "https://api.openany.si/v1/agent-apis/search1api/trending",
"method": "POST",
"content_type": "application/json",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Source of trends: github or hackernews.",
"location": "body",
"name": "search_service",
"nullable": false,
"pointer": "/search_service",
"required": true,
"type": "string"
},
{
"description": "Number of items to return.",
"location": "body",
"name": "max_results",
"nullable": false,
"pointer": "/max_results",
"required": false,
"type": "integer"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "1000",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": []
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Generated request template
Generated from input parameters. Replace placeholder values before use.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 2
Review these request fields before running. Keep the published provider and request method unchanged.
search_service- Source of trends: github or hackernews.
max_results- Number of items to return.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/search1api/trending' \ -X POST \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json' \ --data-raw '{ "search_service": "<search_service>" }'Check the response
No response example is configured. Verify the actual status and response after an approved API call.
Loading related APIs…
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use Search1API Trending with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.