GetPost Search API
PassAudited by ClawScan on May 1, 2026.
Overview
This is a straightforward instruction-only web search API skill, with normal cautions around using a third-party API key, sending search queries to GetPost, and consuming search credits.
This skill appears safe to install if you are comfortable using GetPost as a third-party search provider. Protect the API key, avoid confidential search queries, and monitor credit usage.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Anyone who gets the API key may be able to make searches using the user's GetPost account.
The skill requires a GetPost bearer API key for authentication. This is expected for the service, but the key could allow use of the account or credits if exposed.
Authorization: Bearer gp_live_YOUR_KEY
Use a dedicated API key if possible, do not paste it into shared logs or transcripts, monitor usage, and revoke it if it may have been exposed.
Sensitive or private search terms entered through the skill could be disclosed to GetPost.
The search query is sent to the third-party GetPost API. This is core to the skill's purpose, but users should be aware of the data flow.
curl -X POST https://getpost.dev/api/search ... -d '{"query": "best python web frameworks 2026", "num_results": 5}'Avoid sending confidential queries unless the provider's privacy and retention practices are acceptable for the user's use case.
The user's GetPost credits may be consumed when the agent performs searches.
Each search consumes service credits. This is disclosed and purpose-aligned, but repeated or unnecessary searches could use credits unexpectedly.
Cost: 3 credits per search.
Set expectations for when the agent may search, watch credit usage, and require confirmation for repeated or high-volume searching if credits matter.