Skip to content

Postclick by PPC.io: Landing Page CRO and AI Page Builder status

Answered our latest tool-list check 2 days ago with 21 tools. It will be marked verified after 3 successful checks in 7 days.

Answered (30 days)
2 of 2 checks
Last seen working
17 Nov, 18:16 UTC
Last commit
—
Licence
Not stated

Live checks

We call this hosted server's initialize and tools/list endpoints without credentials, from the public internet, every day for the 2,000 most popular hosted servers and for any whose status changed in the last week, and once a week for the rest. We never call its tools. About AIPoweredBot

  • Answered
  • Needs sign-in
  • No answer
Checked (UTC)ResultResponse timeTools
17 Nov, 18:16Answered0.4 s21
16 Nov, 18:16Answered0.4 s21

Tools (21)

Read from the server on 17 Nov 2026.

list_cro_skills
Find Postclick methods for prioritising page fixes, ad-to-page message match, buyer objections, copy edits and client test briefs. Returns starter requests and portable skill downloads. No account needed.
run_cro_skill
Use when the user wants page fixes, message match, buyer objections, copy rewrites or a client test brief. In your answer, never add free, guarantees, ratings or performance claims unless the source explicitly confirms them. Audit suggestions are not verified facts. Finished copy must not contain placeholders such as $X; choose a useful change supported by the original page. A quote form alone doe
check_balance
Read what the connected Postclick account covers now: its credit balance and how many credits an audit or a build uses, or the pages left on a page plan. Use before starting an audit, design or build, and when the user asks what their account covers. A missing figure is unknown.
audit_page
Start a new landing-page audit when requested. Use check_balance for page coverage and follow the user's permission. First search for existing work when the request concerns a prior audit. Pass campaign context already supplied. Returns an audit_id; use get_audit with wait:25, then run_cro_skill for the requested deliverable. Does not design or build a page.
get_audit
Read audit status, changed progress, server elapsed time and ranked findings with typed edits. Use wait:25 while running. A failed, cancelled or stalled run is not a finished report. Once complete, use run_cro_skill or ask_audit for the relevant buyer, copy or offer evidence. Reading does not authorise a redesign.
get_audit_report
Read the complete stored audit as markdown for a full review. It can be long: use topic or ask_audit for one question, or run_cro_skill for a specific deliverable. Missing and withheld sections remain unknown. Buyer journeys are modelled, not customer research.
get_competitors
Costs nothing. Returns the competitor layer of a finished audit: the competitors bidding on the same clicks, the live ads Google is serving for each of them with the keyword, search volume and CPC behind every one, the landing pages those ads click to, which competitor advertises most, the advertisers currently on this page's own keyword, and the customer's own paid keyword count. The ad and keywo
ask_audit
Uses no credits. Answers one question from a completed audit by returning that part of it in full: small enough to give the user whole, unlike the entire report. THIS IS THE TOOL FOR ANY FOLLOW-UP QUESTION about a page you have already audited. Never answer a question about an audited page from your own summary of it — the audit holds far more than any summary kept, and this is how to get the part
generate_concepts
Draws design directions for an existing audit as rendered pictures. Only when the user asks to see designs: build_page needs none and sets the look itself. Use check_balance for page coverage and follow the user's permission. Returns a run to resume with get_concepts.
get_concepts
Uses no credits. Returns every concept rendered for an audit, each with its image URLs and a link to view it full size, and a runs.active count of how many are still rendering. A pack takes 3 to 8 minutes. While runs.active is above zero, call it with wait set to 300: it holds the connection open and comes back the instant a design lands, the stage moves, or the pack finishes, instead of returning
build_page
Builds a complete HTML landing page for an audit when the user asks and their plan covers it. No design is needed first: the designer sets the look and works the audit's fixes in. Set keep to improve the page they already have and keep its look. Pass concept_id only to build from a design the user saw with get_concepts. Use check_balance to confirm the account covers it. Returns build_run_id. Use
get_build
Uses no credits. Returns the build's status and, once finished, the complete page. A build takes about 10 to 20 minutes, so poll it with wait set to 300: the call holds open and returns the moment the stage moves or the page is ready, which turns a build from dozens of identical reads into a handful of calls that each have something to report. When a call comes back with the same stage you already
share_page
Uses no credits. Mints a public no-login link that anyone can open, including someone with no account. THIS IS THE TOOL FOR 'send me the page' or 'I want to forward this to my client'. Never hand over a dashboard or app link for that: the recipient hits a login wall and sees nothing. Pass build_run_id to share a finished BUILT page: that is what a client should see. Pass concept_id only when the u
export_page
Uses no credits. Packages a finished page as a zip that runs on any static host: index.html with every image it uses pulled into assets/, plus a README and metadata.json. Returns a download link. This is the one for a user who wants the files. share_page is the one for a user who wants something to look at. It also returns implementation_prompt: step by step instructions for putting this page live
describe
List what is in the account when the user asks to see their work. For a page fix, copy rewrite or designer brief, call run_cro_skill directly; no account overview is needed first.
search
Uses no credits. Finds anything in this workspace by words: a domain, a page URL, a client's name, a design's caption, a project. Returns an address for each hit that you pass straight to `fetch`. Use this the moment somebody refers to work they have already done — "the zoomdrain page", "last month's audit", "the report I made for Acme". Leave the words empty to list the most recent of everything.
fetch
Uses no credits. Reads any single thing by its address, which looks like postclick://audit/<id> and comes from `search`, from `describe`, or from any other tool's answer. A plain id works too if that is all you have. `expand` is what makes this worth calling: pass `*` and you get everything attached in one go, which for an audit means the findings, the buyers and their walkthroughs, the competitor
get_asset
Uses no credits. Every design, page capture and logo has an asset_id on the field that holds it. Pass it here. Which form you ask for depends entirely on where the picture is going, and getting it wrong is expensive. `as: "url"` is the DEFAULT AND USUALLY RIGHT one: a public link, no login, full size. Use it for anything you publish with publish_page, and for showing somebody a design. `as: "bytes
publish_page
Uses no credits. Takes HTML you wrote and hosts it at postclick.ppc.io/r/<name>, public, no login, ready to send to a client. A client gets a plain web page, not a link into a chat. We do not template the page, style it or add anything to it: it is exactly the report you wrote. USE PLAIN IMAGE LINKS HERE, from `get_asset` with `as: "url"`. A page we host loads our pictures at full size, so there i
save_note
Uses no credits. Attaches anything you like to any record: who the client is, what they were charged, which findings they have already fixed, when you last sent them a report. Any name, any value. We never look inside it and the audit engine never reads it, so it cannot change what Postclick does. It is there so the work you do around these audits survives between conversations. Saving the same na
get_notes
Uses no credits. Returns the notes saved against one record, or every note in the workspace when no address is given. Worth calling at the start of a repeat job, so a monthly report picks up whatever the last one left behind.