simple, honest pricing

Chrome extension

Not published to the Chrome Web Store yet. The marketing page and pricing comparison table both already say this correctly — this catalog entry was wrong in the prior pass and is now corrected to match them.

verified 2026-08-11

B2B contact search

A shared, workspace-agnostic enrichment corpus sourced from Apollo.io — not a live per-workspace CRM. No automated outreach; export is manual.

verified 2026-08-11

X: Auto Repost

Downgraded from `available` in round 5 by the capability registry, which is the first check that compared the producer against the consumer. x-automations.ts filters post_variants.published_at between two timestamps, but post-dispatch.ts writes only external_id to post_variants — the published_at it sets at the end of a run is on scheduled_posts, a different table. Migration 011 added the column and its comment claims post-dispatch populates it; it never did. The query therefore matches zero rows for every workspace, always has, and no error is raised because an empty result is not an error. Repair is PR D.

verified 2026-08-13

X: Auto Plug

Only replies to your own posts. "Niche" targeting is offered in the UI but never executes — X's API blocks replies to accounts that haven't engaged you.

verified 2026-08-11

X: Auto DM

Configurable in the dashboard but never sends — requires X's dm.write elevated API scope, which PostAI doesn't have. Every run is logged as a failure.

verified 2026-08-11

X: Auto Delete

Downgraded from `available` in round 5. The query does .select("external_id, likes, published_at").lt("likes", minLikes) on post_variants, which has no likes column — 001_initial.sql defines the table and only migrations 011 and 019 have altered it since, adding published_at and ab_group. The PostgREST error goes unchecked, so the job reports success having deleted nothing. A comment 40 lines further down in the same file already acknowledges the column does not exist.

verified 2026-08-13

LinkedIn: Auto Engage / Auto Follow-Up / Content Amplifier / Profile Visitor Alert

Settings save to the database but nothing executes them — no worker or cron reads and runs LinkedIn automation config. Dashboard previously showed fabricated activity counts; that has been removed.

verified 2026-08-11

LinkedIn: Connection campaign planning (target audience, message, schedule)

Building and saving a campaign is real and gated to Creator+. This does not send anything by itself — see linkedin_auto_connect_sending below.

verified 2026-08-11

LinkedIn: Automated invitation sending

Deliberately disabled by a server-side kill switch (LI_AUTO_CONNECT_SEND_ENABLED, unset/false by default in every environment) as of this pass. Before this, an hourly cron decrypted workspaces' LinkedIn OAuth tokens and attempted to send real invitations with no plan gate and no opt-out enforcement (both added), but the send call itself is very likely non-functional regardless: it POSTs a request body shaped for LinkedIn's private/undocumented "Voyager" API to the public v2 REST host, using an OAuth scope (w_member_social) that does not grant invitation-sending permission. Neither the endpoint authorization, the scope, nor the payload has been confirmed against LinkedIn's official documentation or a real developer account. This entitlement stays not_available until that verification happens and the kill switch is deliberately enabled.

verified 2026-08-11

Instagram analytics

Added in round 5. The table, its RLS policies and the reader all exist; the producer does not. There is an x-analytics job and an li-analytics job, and no Instagram equivalent anywhere in apps/jobs. Until round 5 the page filled the gap with a "best time to post" heatmap generated from Math.sin, rendered even when no Instagram account was connected — that has been removed. `producer` is deliberately left unset: the registry test requires a producer that writes what the consumer reads, and inventing one to satisfy it would be the exact failure this registry exists to prevent.

verified 2026-08-13

Employee advocacy

Removed from Pro Plus benefits in round 5. This was sold on a $99 tier with no execution path at all: `advocacy.ts` defines advocacy-notify and advocacy-share-complete, and it is the only file in the repository that references either task — nothing triggers them. The three tables they operate on (advocacy_library_posts, advocacy_members, advocacy_shares) have RLS policies but no producer; the LinkedIn advocacy page writes a draft scheduled_posts row instead, which nothing publishes or notifies on. There is also no member-facing surface to share from. Building it is a feature project (members, invitations, approved library, assignment, share surface, opt-out, share tracking, seat accounting) tracked separately, not a worker connection. Stays `planned` until that ships end to end — partial wiring is not a beta.

verified 2026-08-13

X: DM campaigns

Added in round 5 — this capability previously had no row here at all, despite being the same defect as x_auto_dm, which was correctly disclosed. The campaign pipeline is complete and Creator+ gated, and it runs to completion, but every send fails: sending a DM requires the dm.write scope, and the X OAuth flow never requests it (elevated API access PostAI does not hold). Campaigns therefore end paused or failed. The sender kill switch and the promotion gate are PR D.

verified 2026-08-13