Read the research caps
Returns the caps the research tools enforce server-side, so a client does not have to hard-code them: how many search results, crawl pages, and posts a call may ask for, and how many bytes of scraped text come back in one result. A request above a cap is clamped, not rejected — except a value that is not a positive integer, which is a malformed call.
Returns the caps the research tools enforce server-side, so a client does not have to hard-code them: how many search results, crawl pages, and posts a call may ask for, and how many bytes of scraped text come back in one result. A request above a cap is clamped, not rejected — except a value that is not a positive integer, which is a malformed call.
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/research/caps"{ "maxSearchResults": 0, "maxCrawlPages": 0, "maxPosts": 0, "maxPageBytes": 0}Declare this launch's trust manifest PUT
Records the `PuttyTrustModule` the creator deployed for this token, which is what the Receipts page expands to list the token's modules. Send `null` to withdraw the declaration. The address is a claim, not a verification: the page reads every module from the chain live and drops any that do not answer, so a wrong or stale address makes the page show fewer modules, never more. Requires a launch that has already produced a token address, because the page is looked up by token. A launch belonging to another user returns the same 404 as one that does not exist.
List your research jobs GET
Returns the caller's research jobs, newest first, alongside the daily run budget line. Each entry carries the job's status, the Apify actor that ran it, and `costCents` — the run cost Apify reported against the caller's own Apify account. The figure is informational: Putty does not bill for research runs and does not mark up the cost.