Models
Meta
Multi-agent vs Single Agent Performance

MetaX · Jul 9, 2026 · official

Multi-agent vs Single Agent Performance

Meta's line chart drew 19.4K views on X: 0.5x its median post and #721 of 1,162 AI chart posts we hold by views. Read Oct 12, 2026.

Multi-agent outperforms single agent across latency

XData Line chart Muse Spark All Meta modelsMulti-agentSingle Agent

Meta: Multi-agent vs Single Agent Performance — Published by Meta on X, Jul 9, 2026. Source: x.com

45/ 100

ViralChart score

Small but loved

Fewer views than the median post but a higher engagement rate: a smaller crowd that acted on it.

#683 of 1,162 AI chart posts we hold · #16 of 31 Meta posts. Score = views 40%, likes 30%, engagement rate 15%, save rate 15%, each as a percentile of every AI chart post we hold.

Our read

It sits in the Small but loved quadrant, with a score rank of #683 of 1,162 AI chart posts.

At 0.022 views per follower, this post sits at the 13th percentile among posts with known followers, against a 0.20 median.

Its 1.11% engagement rate lands at the 79th percentile among AI chart posts, above the 0.73% median.

Meta posted 4 items that day, and this one ranked #3 of 4 by views.

0.02views per follower

19.4K views from an account with 865.4K followers.

4posts from Meta that day

Part of a run of 4 posts on Jul 9, 2026. This one was #3 of 4 by views that day.

0.3xthe median line chart post

Across 68 line chart posts we hold, the median gets 73.7K views.

top 21%engagement rate

1.11% of viewers liked, reposted, quoted or replied. The median post gets 0.73%.

Public X numbers from our read on Oct 12, 2026. Peers: 1,162 AI chart posts we hold and 31 from Meta.

Where it sits

Reach against resonance

Each dot is a post. Right is more views, up is a higher engagement rate. The lines are the medians, so the four corners are the four kinds of post.

Among 1,162 AI chart posts we hold

Score #683 of 1,162

Views	19.4K	#721	bottom 38%
Likes	200	#644	bottom 45%
Engagement rate	1.11%	#250	top 21%
Save rate	0.052%	#808	bottom 31%

Among 31 Meta posts

Score #16 of 31

Views	19.4K	#19	bottom 40%
Likes	200	#15	top 47%
Engagement rate	1.11%	#8	top 24%
Save rate	0.052%	#25	bottom 21%

Growth

One read so far

Views19.4K

Age at our read95 days

Views per day of life204views divided by days since it was posted

Dots are our reads. The dotted line from the day it was posted to our first read is a gap, not data.

Meta's posts over time

Every post from this account we hold, by date and views. This one is marked; the line is the running median of the last 10.

News · Jul 9, 2026

Meta's multi-agent latency line chart draws 19.4K views

The July 9, 2026 post reached 19.4K views and a 1.11% engagement rate, landing in the Small but loved quadrant.

What happened

Meta published a line chart on multi-agent vs single agent performance on July 9, 2026. It was one of 4 posts from the account that day, alongside AI Model Benchmark Comparison, Meta Internal Coding Bench, and Vibe Code Bench v1.1 - SWE Atlas Codebase.

The numbers

It drew 19.4K views, ranking #721 of 1,162 AI chart posts by views and #16 of 31 Meta posts by score. Its score rank is #683 of 1,162 AI chart posts.

The lesson

A 1.11% engagement rate at the 79th percentile came with a 0.052% save rate: the line chart drew interaction, but saves stayed low.

What it means

At #16 of 31 Meta posts by score and 0.022 views per follower against a 0.20 median, this chart post reached a small share of the account's followers.

Written by ViralChart from public numbers read on Oct 12, 2026. Every number is checked against our data before it is shown.

Updates: what Meta posted next

Data and API

24 points read off this chart

Estimated from the image 34%

Series	Group	Value	Read
Multi-agent	5k	73	estimated
Multi-agent	6.5k	74	estimated
Multi-agent	8k	75	estimated
Multi-agent	11k	76	estimated
Multi-agent	13k	75	estimated
Multi-agent	15k	76	estimated
Multi-agent	18k	77	estimated
Single Agent	5k	69	estimated
Single Agent	6.5k	69	estimated
Single Agent	8k	69.5	estimated
Single Agent	11k	70	estimated
Single Agent	13k	70.5	estimated

Showing 12 of 24. All points, the redraw and the maker

Max plan · API

GET https://viral-chart.com/api/posts/a6c8a04e659e.json
GET https://viral-chart.com/api/charts/a6c8a04e659e.json
GET https://viral-chart.com/api/charts/a6c8a04e659e.skill.md

Make one like this Open the post JSON Chart data JSON Skill file API docs

Static files in this prototype. The post JSON holds the public numbers, ranks, score, quadrant, our reads and, when checked, our copy.

API · Max

Use this chart via API

On the Max plan you can pull this chart's numbers with the provenance of each one, as JSON or CSV, with its redraw spec, or call it from an agent over MCP. Chart id a6c8a04e659e.

Approximate values. Our two readings of this chart agreed only in part (confidence 0.34 of 1), so check the original before you quote a number. The API marks it lowConfidence, and ?min_confidence=0.5 leaves it out.

See the Max plan API docs

	Path	Returns	Plan
GET	`/api/v1/charts/a6c8a04e659e`	Title, publisher, date, form, point count; with a Max key, the data link	Open
GET	`/api/v1/charts/a6c8a04e659e/data`	Every point with its provenance and confidence, plus the redraw spec. Add ?format=csv for CSV	Max
GET	`/api/v1/charts/a6c8a04e659e/render?view=1`	The draw-only view this page uses	Open
POST	`/mcp`	Tool get_chart_data with this id, for Claude, Cursor and other agents	Max

curlMax

curl -s https://viral-chart.com/api/v1/charts/a6c8a04e659e/data \
  -H "Authorization: Bearer $VIRALCHART_KEY"

Claude CodeMax

claude mcp add --transport http viralchart https://viral-chart.com/mcp \
  --header "Authorization: Bearer $VIRALCHART_KEY"

60 requests a minute per key; over that you get 429 with Retry-After. Up to 5 keys per account, made on your account page and shown once. Without Max, the data route answers 402 with a link to the plans. The numbers describe a chart its publisher owns, and every file carries a license note.