Only WordPress data: the posts AIthor writes and the meta keys it stamps on them, plus standard wp_posts columns like post_status, post_author and post_date. The model vendor still owns the conversation; SleekView only surfaces what is stored in WP.

No. SleekView never calls a model vendor or the AIthor backend. It reads what AIthor has already written to your WordPress database. If a generation never produced a post, it cannot show on the dashboard, which is the honest behaviour.

Yes, as long as AIthor stores the model name in postmeta. Group a Pie or Bar card by that meta key and the dashboard shows the share of generations per model, which feeds straight into cost and quality reviews.

Yes. Group by post_date with an Area or Line card and pick a Count aggregation to see generations per day, week or month. Quarterly content reviews use the trend to argue about cadence with data instead of impressions.

Yes. AIthor's meta is written at creation, so drafts, pending posts and published posts all appear. A Pie grouped by post_status is the fastest way to spot how much generated content is sitting unfinished.

Yes. Add a filter for post_author and every card narrows to that author. Useful for one-on-one reviews and for spotting writers who lean heavily on AIthor without the team realising it.

Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show. Editorial leads use this for quarterly briefings and for archiving a snapshot before a cleanup sprint.

Yes. AIthor can target any writeable post type and SleekView mirrors that. A site generating standard posts and case studies can build per-type dashboards or one combined dashboard scoped by post type.