No. SleekView only reads the wp_posts rows and kafkai_* postmeta that Kafkai already wrote. Every Kafkai generation still goes through the plugin with the key and niche access your subscription manages, so the dashboard never doubles your credit usage.

No. SleekView caches each chart card for the duration you set on the source and runs indexed group-by queries against wp_posts joined to wp_postmeta on the kafkai_* keys. The reads happen in milliseconds and never block Kafkai from saving new drafts.

Yes. Every Kafkai draft is a wp_posts row with a post_author column. SleekView Charts can group by post_author and resolve it against wp_users to rank editors by total kafkai_credit_cost across the month, the quarter, or any custom range.

Yes. Kafkai writes the niche name into the kafkai_niche postmeta on every draft. SleekView reads that key directly, so the niche donut and bar charts only ever show the niches you actually generated articles in, with the live counts.

Yes. SleekView dashboards have a role scope. Save the Kafkai dashboard for editor or content_lead and only users in that role see it, so writers don't see credit costs and finance doesn't have to scroll through draft titles.

Only if the plugin renames the postmeta keys SleekView is reading. The kafkai_article_id, kafkai_niche, and kafkai_credit_cost keys have stayed stable across releases, and SleekView shows a clear error and lets you re-map a key if anything changes.

Yes. Every saved chart view has a shortcode and a block. Drop it on a frontend dashboard page, scope the page to a client role, and the client sees the Kafkai numbers without ever logging into the Kafkai plugin or the Kafkai web app.

Yes. Every SleekView chart card has a CSV export that pulls the same wp_posts rows and kafkai_* postmeta the chart was built on. Use it to hand finance a monthly credit-spend file or to feed an external BI tool, without touching the database directly.