Perplexity launched Teammates in its changelog on 2026-11-06. One of the three sample jobs in that post is competitor tracking. The sample asks a teammate to watch two companies for price changes, launches and new hires. It flags anything important at once and sends a weekly summary (changelog).
Teammates is a research preview for Max only. The help center names Max on individual and Enterprise plans and excludes Pro and Enterprise Pro (help center). Max costs $200 a month or $2,000 a year (Max article, read 2026-11-22). Work that a teammate does uses Computer credits on top of that, at 100 credits per dollar.
We built a competitor-watch setup around that sample. The competitors are four brands of 1 kWh portable power stations: Jackery, Anker, BLUETTI and DJI. Amazon prices and ratings, LinkedIn jobs, and Reddit and X discussion all come from the EveryInfra remote MCP server at https://api.everyinfra.com/mcp. On 2026-11-22, from 12:42 to 12:59 Singapore time, we made 10 live calls to the 5 competitor capabilities and paid $0.010724. One empty Reddit result was refunded. We also made 4 YouTube calls to study the videos, so the whole batch was 13 billed calls for $0.01317.
At catalog prices, watching 30 competitors every day works out to $1.25 to $5.11 a month in data fees. A teammate that writes one research report a day spends $105 to $285 a month in credits, so the data fee is small next to that. We do not have a Max account. The three connection routes and the teammate instructions below are configuration examples based on the docs, and we did not run them inside Perplexity.
Two results from the live calls change what a teammate would report. A LinkedIn job search for "Jackery" returned 20 jobs, and none of them was at Jackery. An X search with sort=latest returned 25 posts, and 6 of them were more than a month old.
The oldest was from November 2024. Both need a filter rule in the teammate's instructions. Without one, the weekly report can list another company's hires and a two-year-old sale as new moves.
Key takeaways
- Teammates reached the web on 2026-11-06 and the Mac app on 2026-11-13. It is a research preview for Max only: $200 a month or $2,000 a year for individuals, or an Enterprise Max seat. New teammates use Claude Opus 5.5 by default.
- The Perplexity help center documents custom remote connectors (None, API Key or OAuth) and a custom API credential vault. The connector form has no field for custom request headers, apart from two Cloudflare Access headers. The EveryInfra
/mcpendpoint accepts onlyAuthorization: Bearer. The public docs do not say which header the connector's API Key mode sends. The credential vault lets you write the header, and the Agent APImcptool takes the token directly. We did not run any of the three routes inside Perplexity.- We made 10 live calls to 5 competitor capabilities from 12:42 to 12:59 Singapore time on 2026-11-22 and paid $0.010724. An empty Reddit result was refunded. Rate limits came back with
retry_afterand no charge.- Estimated at catalog prices for 30 competitors a day: Amazon prices only cost $1.25 a month. Add daily Reddit and X plus weekly jobs and reviews, and the total is $2.91. All six capabilities every day cost $5.11.
- One raw LinkedIn job response held about 24,230 tokens. At the Opus 5.5 input price, that is $0.097, or 174 times the $0.000556 data fee for the call. Filter first, then let the model read.
The teammate reads data and writes summaries. The key stays in the connector or the credential vault, and the model never sees its value. Generated illustration based on the Perplexity help center article on credentials
What Perplexity Teammates are
Teammates are long-running agents built on Perplexity Computer. The help center defines a teammate as an agent that owns ongoing work. You give it a responsibility, such as triaging bug reports, tracking metrics or researching a market. It plans the tasks and follows through until the result is ready for your review. Compared with a one-off Computer task, it adds five things.
It splits a goal into tasks and runs them in parallel across several agents. It has its own desktop and browser. It watches the tools you connect. It keeps its role and memory between conversations. You can choose a model for each teammate.
Teammates in the same Project share files and instructions, and they can message each other. You can also tag them as apps in Slack, GitHub and Linear. This matters for competitor work, because one teammate can collect data while another one writes the weekly report.
| Item | Detail | Source (read date) |
|---|---|---|
| Launch | Web on 2026-11-06; Mac app on 2026-11-13 | Changelog; 9to5Mac |
| Plans | Individual Max, Enterprise Max seat. Not Pro or Enterprise Pro | Help center, 2026-11-22 |
| Status | Research preview. Behavior may change | Same |
| Default model | Claude Opus 5.5, changeable per teammate | Same |
| Platforms | Web, mobile apps, desktop apps | Same. The product page lists Windows and Android as coming soon |
| Enterprise | Admins grant access by role. Uses Computer credits, personal allowance first and then the org pool. The teammate stops when its creator leaves | Teammates for Enterprise, 2026-11-22 |
The setup steps in the help center are short. Hover over Teammates in the sidebar and select the plus button, labeled Create teammate. Enter a name in Name or role and pick an appearance. Open Advanced to add instructions or a schedule, then select Create. You finish the setup in the chat that opens.
Tools are also connected from that chat. You ask the teammate to "Connect Slack", sign in, and review the permissions. For a tool that you already installed, open Plugins in the right-hand panel and select Use a plugin. The help center suggests four parts for each job: the source of the work, the output, the schedule or trigger, and the audience.
Perplexity Teammates pricing: Max plus Computer credits
Teammates pricing has two layers. First you need Max. Then the work that a teammate does uses Computer credits.
We quote Max prices only from Perplexity pages. The help center Max article says $200 a month or $2,000 a year. The Max purchase page shows $167 a month billed yearly, plus a limited-time "+$450 free Computer credits" offer (Max page, read 2026-11-22).
| Item | Number | Source (read 2026-11-22) |
|---|---|---|
| Max, monthly billing | $200 a month | Perplexity Max article |
| Max, yearly billing | $2,000 a year ($167 a month on the purchase page) | Same; Max page |
| Credit rate | 100 credits = $1 | Credits article |
| Max monthly credits | 10,000, no rollover | Same |
| One-time bonus for new subscribers | 35,000, expires in about 30 days | Same |
| Enterprise Max monthly credits | 15,000 per seat | Same |
| Order of use | Bonus, then plan, then purchased | Same |
| Typical task cost | Quick fact 15–70; multi-step research report 350–950; data dashboard 2,400–9,800 | Same |
The credits article adds one more rule. A normal Ask search does not use credits. Computer tasks do, and teammate work counts as Computer tasks. The Teammates article says that heavy projects use more credits, especially with parallel agents, large files or frequent automations. You can check usage on the Usage page, and you can turn auto-refill on or off there.
Two videos describe the price differently from the pages that we read on 2026-11-22. Video O1RM24jF_HE splits the $450 offer into the 35,000 bonus credits plus one month of the 10,000 credits that Max includes anyway. It concludes that about $100 of the offer is the normal first month. It also quotes the help page of that time, which said that teammate usage was free on Max for a promotional period (YouTube). The "Usage and credits" section that we read has no sentence about a free promotion.
It says only that teammates use the monthly credit allocation of Max. A Reddit user reports a separate teammate allowance that runs out, as we show later. For a budget, plan with credits. The video also gives November 4 as the launch date. The changelog date is 11/06/26, and this article uses the changelog date.
Which data a competitor watcher needs
Competitor tracking covers three things: prices, new products and hiring. Discussion on social platforms is a fourth. Each one maps to a capability in the EveryInfra catalog. We read the free catalog at 12:41 Singapore time on 2026-11-22.
The unit prices and availability in the table come from that read. The TikTok Shop product list, tiktok/shop_products, was marked unavailable at that time. The product review capability, tiktok/shop_product_reviews, was available.
| What to watch | Capability | USD per call | Suggested frequency |
|---|---|---|---|
| Amazon price, list price, rating, rank | amazon/profile |
0.001389 | Daily |
| New Amazon products for a keyword | amazon/search |
0.002236 | Weekly |
| Amazon featured reviews | amazon/reviews |
0.001389 | Weekly |
| Hiring | linkedin/jobs |
0.000556 | Weekly |
| Reddit discussion | reddit/search |
0.000792 | Daily |
| X discussion | twitter/search |
0.000792 | Daily |
| TikTok Shop product reviews | tiktok/shop_product_reviews |
0.000764 | Daily or weekly |
The catalog explains each parameter, and a few of these notes change the results. The time range of reddit/search is fixed at the last month, and the sort order does not change that range. A keyword of three words or more must match three quarters of the words. When nothing matches, the empty result is refunded.
The twitter/search notes say that latest is only a preference and does not guarantee strict time order. The keyword can use X search operators such as from: and since:. The amazon/reviews capability returns only the featured reviews on the product page, which are usually about a dozen per product. We ran into the first two in the live calls. We did not call amazon/reviews this time, so that note comes from the catalog.
Where the key goes: three ways to connect
The EveryInfra /mcp endpoint accepts only the request header Authorization: Bearer <key>. Since 2026-11-04 it no longer accepts a key in the URL as ?key=. A request without a key gets "no API key provided" and no charge. So you cannot pick None as the auth type and put the key in the URL.
Perplexity has three places where a key can live. Each one is documented to a different level of detail.
| Route | Where you set it | How the key is stored | Do the docs name the header? | Status in this article |
|---|---|---|---|---|
| A. Custom remote connector | Settings, Connectors, or a plugin mcp.json
|
Saved by the connector, auth type API Key | No | Configuration example |
| B. Custom API credential plus REST | A Computer task, saved to the personal vault or a project | Encrypted, injected by a secure proxy, hidden from the agent and sandbox | Yes: tokens, custom headers, query parameters, Basic auth | Configuration example |
C. Agent API mcp tool |
Your own code or scheduler | Your own secret store. Pass authorization or headers
|
Yes | Configuration example |
Three auth options for custom remote connectors. The form cannot add custom request headers. Screenshot of the Perplexity help center, read 2026-11-22
Route A: custom remote connector (configuration example)
The help center article "Adding custom remote connectors" says that these connectors send standard MCP requests. The auth options are None, API Key and OAuth. For API Key, it advises you to "use a key with the narrowest access". The OAuth redirect URL is https://www.perplexity.ai/rest/connections/oauth_callback.
Dynamic client registration works, and you can also enter a client ID and secret by hand. Custom connectors have been open to Pro, Max and Enterprise since 2026-03-12 (changelog). A plugin can also bundle up to 15 MCP servers in mcp.json, with type streamable-http, http or sse (custom plugin article).
The problem is the API Key option. The page does not say which request header Perplexity puts the key in. EveryInfra accepts only Authorization: Bearer. If Perplexity uses a different header name, the first call gets "no API key provided".
EveryInfra OAuth is open only to registered clients, which today are claude.ai and chatgpt.com. Perplexity is not one of them, so OAuth is not an option either. We do not have a Max account, so we could not add the connector inside Perplexity. The block below is a configuration example based on the help center.
{
"mcpServers": {
"everyinfra": {
"type": "streamable-http",
"url": "https://api.everyinfra.com/mcp"
}
}
}
Test it like this after you add it. Ask the teammate to call everyinfra_list_capabilities, which reads the catalog at no charge. Then ask for one amazon/profile call.
A reply of "unauthorized: no API key provided" means that the API Key mode sends a different header. In that case, use route B or C. A result with billing.charged_usd means that the connector works.
The first step alone is not enough. At 12:42 on 2026-11-22 we checked the EveryInfra side with requests that carried no key. The MCP initialize call still returned HTTP 200 and the server instructions, because it does not need auth. Only tools/call returned isError: true, code: unauthorized and retryable: false, with the note "Nothing was charged". So a connector that shows as connected in Perplexity may still send the key in the wrong place. Make one billed call and look for billing.charged_usd before you trust it.
Check which header the API Key mode sends (method, not run by us)
Route A works only if Perplexity puts the key in the right header. The help center does not say which one, but you can find out in ten minutes before you connect EveryInfra. Run a small server that only prints the request headers, and expose it on a temporary public HTTPS address. Add that address in Perplexity as a custom remote connector with API Key auth, and enter a fake key that is easy to spot, such as probe-7f3a.
When you save the connector or make the first call, Perplexity sends an MCP initialize request. Look for the fake key in the printed headers. If it is in Authorization with the prefix Bearer, route A works as is. If it is in another header, such as X-API-Key, skip route A and use route B or C.
# header_probe.py: print the request headers only. No MCP, replies 401.
from http.server import BaseHTTPRequestHandler, HTTPServer
class Probe(BaseHTTPRequestHandler):
def do_POST(self):
for name, value in self.headers.items():
print(name, "=", value)
self.send_response(401)
self.end_headers()
do_GET = do_POST
HTTPServer(("127.0.0.1", 8787), Probe).serve_forever()
A tunnel such as cloudflared tunnel --url http://127.0.0.1:8787 gives you the temporary public address. We did not run this inside Perplexity. Use it only to read the header name, with a fake key, and delete the connector afterwards. Never put a real key into a server that prints its request headers.
Route B: credential vault plus the REST API (configuration example)
The changelog of 2026-07-27 added "Connect Computer to any API securely". A service may have no built-in connector. You can then add a credential for one task, save it to your personal vault, or share it with a project. The raw secret stays out of the agent's activity and sandbox (changelog). The help center credential article lists the supported forms: tokens, custom headers, query parameters and Basic auth.
A secure proxy injects the secret. New credentials default to "Always allow", and you can change that to "Ask for approval". If an API echoes the secret back, Computer can see it (credentials article). EveryInfra responses do not echo the key.
The benefit of this route is that you write the header yourself. Set the name to Authorization and the value to Bearer plus the key, which matches what EveryInfra expects. The teammate then uses the REST endpoint POST /api/v1/social instead of MCP. The parameters are the same as for the MCP tool everyinfra_call_api. With the credential saved, each request that the teammate sends is equal to this one.
curl -s https://api.everyinfra.com/api/v1/social \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"platform":"amazon","action":"profile","params":{"url":"https://www.amazon.com/dp/B0D7PPG25F"}}'
We ran this curl four times on our own machine for amazon/profile. We did not run the save and inject steps inside the Perplexity vault, so that part is a configuration example.
Route C: build it with the Agent API (configuration example)
You may not have Max, or you may want to own the schedule, filters and retries. In that case, build your own "teammate" on the Perplexity Agent API. Its mcp tool takes server_url (Streamable HTTP only), authorization (the raw token, which the docs say is never logged or echoed), headers, allowed_tools, require_approval and defer_loading. MCP tool calls are free, and only model tokens are billed (Agent API MCP docs). You can also save the server as a custom connector in the API Console and refer to it with type: "connector" (connectors docs).
curl https://api.perplexity.ai/v1/agent \
-H "Authorization: Bearer $PERPLEXITY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "anthropic/claude-haiku-5-5",
"input": "Check today'"'"'s Amazon price for B0D7PPG25F and report only if it differs from 559.",
"tools": [{
"type": "mcp",
"server_label": "everyinfra",
"server_url": "https://api.everyinfra.com/mcp",
"authorization": "'"$EVERYINFRA_API_KEY"'",
"allowed_tools": ["everyinfra_call_api", "everyinfra_get_job"],
"require_approval": "never"
}]
}'
The allowed_tools field narrows this route. The default EveryInfra MCP exposes 12 tools, and their 12 descriptions in tools/list add up to 9,209 characters. Some of them, such as support tickets, account details and top-up links, have nothing to do with competitor work. With only everyinfra_call_api and everyinfra_get_job in the list, the model cannot see or call the others.
For the schedule, a daily cron job is enough. For large volumes, the Batch API takes up to 50,000 requests at once. We did not run the block above with a Perplexity key, so it is a configuration example. The EveryInfra MCP request format inside it is the one that we tested.
Scheduling and storage when you build it yourself
Route C means that you supply three things that a teammate has built in: a schedule, memory and delivery. The schedule is the simple part. A cron job or a cloud scheduler can run once a day at 09:00 Singapore time. For memory, a small database or a JSON file is enough.
Store yesterday's price for each ASIN, the post IDs already seen for each brand, and the list of ASINs from each week. Each run reads that state, compares, and writes it back. For delivery, a Slack webhook can post only when something changed.
Use two model tiers. The daily comparison can run on a cheap model, such as anthropic/claude-haiku-5-5. The Agent API models page lists it at $0.10 per million input tokens up to 100,000 tokens. That model only needs to decide whether a few fields changed since yesterday. Use anthropic/claude-opus-5-5 only for the Monday report.
If the comparison is simple enough for plain code, skip the model on daily runs. Then the only daily cost is the EveryInfra data fee. You can also pin the version of an Agent API effort level. A pin protects a scheduled job from a default model change, such as the one on 2026-11-18 (Effort docs).
How to choose a route
The table sums up the trade-offs, and the notes after it explain the two main choices.
| Your situation | Route | Why | Cost |
|---|---|---|---|
| You pay for Max and work inside Perplexity | A first | The teammate reads the tool descriptions and fixes bad parameters from the 422 reply | The auth header is not documented, so test it once |
| Route A fails the auth check | B | You write the header name and value yourself | The teammate builds REST requests from your instructions |
| No Max, or a high volume | C | Token billing, allowed_tools, require_approval
|
You write the schedule, retries and storage |
| You want the teammate never to touch the data key | C plus a teammate | Your server pulls data and posts to Slack, and the teammate reads Slack | Two systems to run |
Route A is the easiest when it works. Add the connector and check the auth header with one read-only call. When a parameter is wrong, the server returns a 422 that lists the allowed values, and the model can fix the call itself.
Route C suits a team with an engineer. A small model can do the daily comparison and a large model can write the weekly report, which keeps the cost low. The allowed_tools field fixes the tool scope inside the request, which is more reliable than a reminder in the instructions.
How to narrow permissions
The first layer is the EveryInfra key. The console can limit a key by platform, product and capability. Tick only amazon/profile, amazon/reviews, reddit/search, twitter/search and linkedin/jobs. Then set a total USD spend limit on the key.
When the key reaches the limit, the API returns 403 key_spend_limit_reached and stops charging. By the math later in this article, 30 competitors cost at most $5.11 a month, so a $10 limit is enough. Give this key to the teammate only, and issue a separate key for every other program. When something goes wrong, you can then stop one key without stopping the rest.
The second layer is the MCP tool list. Route C uses allowed_tools to expose two tools only. Route A has no such field inside Perplexity.
There, write in the instructions that the teammate may use only everyinfra_call_api, and rely on the first layer to enforce the scope. The MCP security guidance lists scope minimization as a practice. It also discusses token passthrough and the confused deputy problem (MCP security best practices).
The third layer is the Perplexity credential. A vault credential defaults to "Always allow". With "Ask for approval", the teammate asks you before each use. A daily schedule would stall on that prompt.
A more practical choice is to keep "Always allow" but save the key only in your personal vault and not share it with a project. Other teammates in the project then cannot use it. Enterprise admins can also limit each connector to selected roles, as the changelog of 2026-10-19 describes.
The fourth layer is spend. Perplexity has no budget per teammate. The Enterprise article says so directly, and individual plans rely on the Usage page and the auto-refill switch. EveryInfra has a spend limit per key. Each side controls its own bill.
Live calls: 12:42 to 12:59 Singapore time on 2026-11-22
We used a test key on our own machine in four rounds and tested both REST and MCP. Each time, duration and charge in the table comes from the response and the local log.
| Singapore time | Method | Capability | Parameters | Result | Duration | Charge (USD) |
|---|---|---|---|---|---|---|
| 12:42 | REST | amazon/search |
portable power station 1000wh | 10 products | 22.2 s | 0.002236 |
| 12:42 | REST | amazon/profile |
Jackery B0D7PPG25F | $559, 4.7 stars, 3,753 ratings | 9.0 s | 0.001389 |
| 12:49 | MCP | linkedin/jobs |
Jackery, United States | 20 jobs, 0 at Jackery | 34.0 s | 0.000556 |
| 12:50 | MCP | reddit/search |
Jackery Explorer 1000 v2, newest | 0 posts, refunded | 4.5 s | 0 |
| 12:55 | REST | amazon/profile |
Anker B0FN7MSY4L | $469.99, list price $799 | 9.3 s | 0.001389 |
| 12:56 | REST | amazon/profile |
BLUETTI B0F42CSQWG | $549, list price $899 | 26.0 s | 0.001389 |
| 12:56 | REST | amazon/profile |
DJI B0H2MFBDZL | $469.99, list price $699 | 11.1 s | 0.001389 |
| 12:57 | MCP | reddit/search |
Jackery, newest | 8 posts | 4.8 s | 0.000792 |
| 12:58 | MCP | twitter/search |
Jackery, latest | 25 posts, 6 older than 30 days | 11.1 s | 0.000792 |
| 12:59 | MCP | twitter/search |
Jackery since:2026-11-15, latest | 25 posts, 24 within 7 days | 11.9 s | 0.000792 |
During research we also made one youtube/search call ($0.000778) and three youtube/transcript calls ($0.000556 each) to check what videos show. All 13 billed calls cost $0.01317. The 10 competitor calls cost $0.010724.
The test key is limited to 10 requests a minute and is shared with other tests. Over the whole batch we hit the limit 7 times. Five were youtube/transcript calls during research: three sent in the same second at 12:45, then one at 12:46 and one at 12:47. One was an amazon/profile call at 12:54. These 6 used REST and got HTTP 429, with a retry_after of 11 to 30 seconds.
The seventh was a reddit/search call at 12:56 over MCP. Its HTTP status was 200, but isError was true, and the structuredContent.error object held code: rate_limited, retry_after: 5 and max_retries: 3. All 7 replies said "Nothing was charged", and each retry about a minute later worked. A teammate's instructions should say: on rate_limited, wait retry_after seconds and retry, at most 3 times. Without that rule, it may report a rate limit as "no data today".
| Singapore time | Method | Capability | Status | retry_after |
Retry |
|---|---|---|---|---|---|
| 12:45:30 | REST |
youtube/transcript, three videos in one second |
HTTP 429 | 30 s (only one of the three replies was saved) | Worked between 12:47 and 12:49 |
| 12:46:35 | REST |
youtube/transcript 8S1XRdVXTYE |
HTTP 429 | 25 s | Worked at 12:47:38 |
| 12:47:49 | REST |
youtube/transcript vC87aSkXeK0 |
HTTP 429 | 11 s | Worked at 12:48:52 |
| 12:54:45 | REST |
amazon/profile Anker |
HTTP 429 | 15 s | Worked at 12:55:47 |
| 12:56:55 | MCP |
reddit/search Jackery |
HTTP 200, isError true |
5 s | Worked at 12:57:57 |
REST and MCP return the same data in different wrappers. REST returns JSON, with results, billing and refund at the top level. MCP answers in JSON-RPC, and the data is a JSON string in result.content[0].text that needs a second parse.
On errors, MCP adds structuredContent.error, whose retryable and max_retries fields are hints for agents. A teammate on route A sees the MCP layer, and a teammate on route B sees the REST layer. Field names in the instructions must match the route.
Empty results are refunded. Rate limits return retry_after, also with no charge. Screenshot of an EveryInfra MCP API response, 12:50 and 12:56 Singapore time on 2026-11-22, balance fields removed
What a teammate sees when a call fails
The agent runs every day with nobody watching. Its reports are reliable only if it can tell when to wait, when to fix a parameter and when to stop. EveryInfra error replies are sentences that a model can read, and each one says whether a charge happened. The table lists the cases that we saw in the live calls or in the catalog notes.
| Case | What comes back | Charge | What the teammate should do |
|---|---|---|---|
| No key, or a wrong header | "unauthorized: no API key provided" | None | Stop and report an auth problem |
| Bad parameter | 422 with the allowed values | None | Fix the parameter once |
| Rate limit | REST 429, or MCP rate_limited with retry_after
|
None | Wait, then retry up to 3 times |
| Key spend limit reached | 403 key_spend_limit_reached
|
None | Stop for the day and tell you |
| Source temporarily unavailable | 503 | None | Retry later, then report "not collected" |
| Nothing found | 200, empty_result_refunded
|
Refunded | Report "no new items" |
Treat an empty result and a failure differently. The Reddit search for the full model name returned 0 posts. Its billing.reason was empty_result_refunded and its refund status was succeeded. That is a true "nothing found", and the report can say "no new posts".
When a data source is temporarily unavailable, the server returns 503 and does not disguise it as an empty 200. The teammate should retry once or twice that day. If the call still fails, the report should say "not collected today", not "no change".
Amazon prices: three brands show a list price
All four brands sell a 1 kWh LiFePO4 portable power station, and amazon/profile returned close prices in the same half hour. The Jackery Explorer 1000 v2 was $559. The Anker SOLIX C1000 Gen 2 and the DJI Power 1000 V2 were both $469.99. The BLUETTI Elite 100 V2 was $549. The difference was in the list price.
Anker, BLUETTI and DJI all returned a list_price of $799, $899 and $699. Against those list prices, the discounts are about 41%, 39% and 33%. The Jackery result had no list price. The calls came one week before Black Friday, and the Jackery Japan account on X announced "up to 52% off" on 2026-11-20. A daily price report that reads only the current price cannot show who is discounting, or by how much.
The amazon/profile response also includes bestseller_ranks. In the Outdoor Generators category, Anker was number 1, Jackery number 2, BLUETTI number 9 and DJI number 27. Rating counts were 3,753 for Jackery, 1,856 for BLUETTI, 1,823 for Anker and 836 for DJI. The seller field helps too.
The seller_name on the DJI listing was Yeehui Innovations, not a brand store. When you track prices, you need to know which seller's offer you are reading. Our article on Amazon price tracking with comparable offers covers how to compare several sellers on one ASIN.
New products: search a keyword once a week
Prices need a daily check, but a weekly check is enough for new products. At 12:42 we searched amazon/search for "portable power station 1000wh". The first page held the 10 products below. Store each week's ASIN list, search again the next week, and compare. Then call amazon/profile once for each new ASIN to get the details.
| ASIN | Brand | Model | Price (USD) | Rating (count) |
|---|---|---|---|---|
| B0C1SMJTDT | BLUETTI | AC180 | 549 | 4.5 (2,677) |
| B0GVJ5X7RP | STARYLINE | 1024Wh 1000W | 339.99 | 4.2 (9) |
| B0D62GMQ3F | Anker | SOLIX C300 | 279.99 | 4.6 (1,991) |
| B0D76BH4HX | Daran | 288Wh 600W | 279.99 | 4.3 (278) |
| B0FN7MSY4L | Anker | SOLIX C1000 Gen 2 | 469.99 | 4.6 (1,823) |
| B0F42HLLSC | BLUETTI | Elite 30 V2 | 329.99 | 4.5 (1,347) |
| B0F42CSQWG | BLUETTI | Elite 100 V2 | 549 | 4.5 (1,856) |
| B0D7PPG25F | Jackery | Explorer 1000 v2 | 559 | 4.7 (3,753) |
| B0H2MFBDZL | DJI | Power 1000 V2 | 469.99 | 4.4 (836) |
| B0HD6GN86Q | BLUETTI | Elite 100 mini | 379.99 | 4.5 (1,856) |
Two leads on this page are worth a report. The STARYLINE 1 kWh unit had only 9 ratings and cost $339.99. That is at least $130 below the four big brands, and it looks like a typical new entrant.
The BLUETTI Elite 100 mini and Elite 100 V2 both had 1,856 ratings. The two listings share one variation review pool on Amazon. When you track rating changes, group them by parent ASIN and do not count them as two separate products.
Read the order of search results with care, because it changes by time and place. A weekly report should say "these ASINs appeared on page one this week" rather than "who ranks where". After you add a new ASIN to the competitor list in the project, the daily price check covers its price and rating from then on.
How to detect a price change: keep yesterday's snapshot
A teammate has long-term memory and can read and write files in a project. A practical design is a snapshot.json file in the project. Each daily run reads yesterday's snapshot, calls amazon/profile, and compares five fields: price, list_price, in_stock, seller_name and rating_count.
A price rise or drop, a list price that appears or disappears, an out-of-stock state, or a new seller are all worth a report. A big jump in rating count in one day may point to a promotion or a launch push. After the comparison, the run writes today's values back to the snapshot for the next day.
Put fixed thresholds in the instructions, and do not let the model decide each day. For example, report a price change above 2%, a daily rating count increase above 1%, and any change in in_stock. Without thresholds, the model may report the gap between $469.99 and $469.98, or it may treat a 20% drop as noise. The chart above shows the snapshot of the four brands on one day. Comparing the next day's numbers with it is the whole daily job of the teammate.
TikTok Shop: reviews by product
On the TikTok Shop side, tiktok/shop_product_reviews was available in the catalog at $0.000764 a call. Its required parameter is product_id. Optional parameters are country, rating, sort and page_token for paging. The shop product list, tiktok/shop_products, was marked unavailable when we read the catalog on 2026-11-22. So you first find competitor product IDs by hand or with tiktok/shop_search, and you save them in the list.
After that, a daily run fetches reviews by ID. Use rating to fetch only one-star and two-star reviews if you want to track complaints. We did not call this capability in this test, and the parameters come from the catalog notes. One X post in our results said "Got it on TikTok shop", which shows that these products sell there. The platform page is TikTok Scraper API.
LinkedIn hiring: 20 jobs, none at Jackery
At 12:49 we searched linkedin/jobs for the keyword "Jackery" with location "United States" and got 20 jobs. By the company_name in the response, Joby Aviation had 5, Jack had 3, JAC Recruitment had 3, and 9 other companies had 1 each. Those 9 were Jacques Marie Mage, Jackson James, Jobot, Jazwares, Pair Eyewear, JAKKS Pacific, Kickmaker, YQN Logistics and Janie and Jack. Jackery had 0. The keyword match is fuzzy, so companies with similar names come back.
Suppose the instructions say only "see who Jackery hired lately". The model gets 20 results and may well list a Joby Aviation aircraft engineer job as "Jackery is hiring". The instructions must say: keep only jobs whose company_name equals the competitor name, ignoring case.
When nothing matches, the report should say "no new jobs this week". LinkedIn's own Job Posting API serves applicant tracking partners and is not taking new partners (Microsoft Learn). Use of job data is also subject to the LinkedIn jobs terms. The platform page is LinkedIn Scraper API.
X and Reddit: pair sort=latest with since:
At 12:58 we searched twitter/search for "Jackery" with sort=latest and got 25 posts. Thirteen were in Japanese and twelve in English. Twelve were from the last 7 days, and six were more than 30 days old. The oldest was a Black Friday post by the Jackery Japan account on 2024-11-14.
The catalog note already says that latest does not guarantee strict time order. At 12:59 we changed the keyword to "Jackery since:2026-11-15" and called again. All 25 posts were from 2026-11-15 or later, and 24 fell within 7 days of the call. The other one was posted at 08:14 Singapore time on 2026-11-15, 7.2 days before the call. Of the 25, 22 were in English and 3 in Japanese. The charge was the same, $0.000792.
Several of these 25 posts belong in a report. The Jackery Japan account announced a Black Friday sale of up to 52% off on 2026-11-20. On 2026-11-21 it announced a live stream for 2026-11-24. On 2026-11-22 it posted from a disaster-preparedness fair in Akasaka, Tokyo.
Among the English posts, one shared a deal of up to 54% off, and one user said that they bought a unit on TikTok Shop. Put "since: plus the date of the last run" into the instructions. Each daily run then gets only new posts, with no repeats and no gaps.
On Reddit, the 12:50 search for the full model name "Jackery Explorer 1000 v2" returned 0 posts. The empty result was refunded by rule, and the charge was 0. At 12:57 we searched the brand name and got 8 posts, all from 2026-11-20 and 2026-11-21. All 8 mention Jackery in the title or body. One complaint about after-sales service in r/Portable_PowerStation had the title "Buyer Beware".
Two side-by-side comparison posts came from r/4x4Compare, and one question in r/Jackery asked about extending solar panels. Reddit search covers only the last month, which suits a daily run. The same post will be in tomorrow's results too, so the teammate must drop duplicates by post id. The Reddit Data API Terms set the rules for data use.
How many tokens a raw response costs
Each time a teammate reads a raw API response, it pays for the model input tokens. We estimated the size of each response at about 4 characters per token. Then we priced it at $4 per million input tokens for anthropic/claude-opus-5-5, from the Perplexity Agent API models page (model prices, read 2026-11-22). Teammates bill in credits and do not publish a token price. We use these numbers to compare sizes.
The largest response was LinkedIn. The MCP text held 96,919 characters, or about 24,230 tokens, because every job came with its full description. At the Opus 5.5 input price, that is about $0.097, or 174 times the data fee for the call.
And none of the 20 jobs was useful. The 25 X posts came to about 10,142 tokens. Each post carried more than 30 fields, such as author bio, avatar URL and follower count.
The way to save is to filter first and let the model read after. On route C, your own code can call REST, drop unrelated companies and old posts, and pass only a few fields to the model. Routes A and B have no code layer of your own.
There, ask the teammate in the instructions to write a short filter script first, because Computer can run code, and to read the filtered result. Our article on Claude Code Channels for competitor post alerts uses the same idea. A subagent returns only a summary, and the main session never reads the raw data.
How long one run takes
Time matters as well as money. In our test, the fastest call took 4.5 seconds (the empty Reddit result) and the slowest took 34.0 seconds (20 LinkedIn jobs). The four amazon/profile calls took 9.0 to 26.0 seconds. Tier B makes 90 calls a day, three for each of 30 competitors.
At an average of 12 seconds a call in sequence, that is 18 minutes. With a key limit of 10 requests a minute, the queue alone takes 9 minutes. A teammate can run agents in parallel, but more parallel agents hit the rate limit sooner. After a hit, the agent must wait for retry_after.
Two methods make a run shorter. First, ask for a higher per-minute limit on the key, or state a maximum request rate in the instructions. Second, use async mode. Add "mode":"async" to the request body, and the server returns a job_id at once.
Then fetch the result with everyinfra_get_job or GET /api/v1/jobs/{job_id}. The async_hint field in each response points to this option. For a teammate, async mode means it does not wait on the slow requests. The cost is one extra polling step, so the instructions must say how often to poll and when to give up.
What watching 30 competitors a day costs
Here are three setups for 30 competitors at the catalog prices of 2026-11-22. A month has 30 days and 4 weekly runs. Empty results are refunded, so real bills come in lower.
To be clear about the method: we called 4 brands, and the 30-competitor figures scale the unit prices in a straight line. They assume the same number of calls per competitor each day, a billed result every time, and no retries after rate limits (a rate limit costs time, not money). What changes with more brands is the size of each response. Busy brands return longer X and Reddit results, so the model reads more tokens, but the data fee stays the same.
| Tier | What it runs | Calls a month | USD a month | USD a day |
|---|---|---|---|---|
| A |
amazon/profile daily |
900 | 1.25 | 0.042 |
| B |
amazon/profile + reddit/search + twitter/search daily; linkedin/jobs + amazon/reviews weekly |
2,940 | 2.91 | 0.097 |
| C | All six capabilities daily, including amazon/reviews, linkedin/jobs and tiktok/shop_product_reviews
|
5,400 | 5.11 | 0.170 |
A few lines of Python reproduce the math, with unit prices taken from price_usd in the catalog.
P = {"amazon/profile": 0.001389, "amazon/reviews": 0.001389, "reddit/search": 0.000792,
"twitter/search": 0.000792, "linkedin/jobs": 0.000556, "tiktok/shop_product_reviews": 0.000764}
N, DAYS, WEEKS = 30, 30, 4
a = N * DAYS * P["amazon/profile"]
b = N * DAYS * (P["amazon/profile"] + P["reddit/search"] + P["twitter/search"]) \
+ N * WEEKS * (P["linkedin/jobs"] + P["amazon/reviews"])
c = N * DAYS * sum(P.values())
print(round(a, 2), round(b, 2), round(c, 2)) # 1.25 2.91 5.11
Next to the teammate's own credits, the data fee is small. The credits article gives 350 to 950 credits for a multi-step research report. One report a day is 10,500 to 28,500 credits a month, or $105 to $285.
That is more than the 10,000 monthly credits in Max. One report a week is 1,400 to 3,800 credits, or $14 to $38, which fits in the monthly allowance. The $2.91 of tier B is only 1.0% to 2.8% of the credit cost of a daily report.
So the budget depends on how often the teammate runs and how much raw text it reads each time. One workable plan is a light daily run that only fetches, compares and posts to Slack on changes. A full report then runs once a week, on Monday. Our article on a price monitoring subscription product works out the cost structure for turning this kind of monitor into a product.
Credits per run: we did not measure them
Perplexity does not publish a credit price for each step of a teammate. It gives task-level ranges only. We did not measure how many credits a light daily run (fetch, compare, post on change) uses, because we have no Max account and there is no per-step price to convert. The table uses only the help center range for research reports.
| Run | Credits each (help center range) | Runs a month | Credits a month | USD a month |
|---|---|---|---|---|
| Weekly full report | 350–950 (research report range) | 4 | 1,400–3,800 | 14–38 |
| Daily full report | 350–950 (research report range) | 30 | 10,500–28,500 | 105–285 |
For the daily run, measure it. Note the credit balance on the Usage page before and after a trial day, and divide the difference by the number of runs that day. Average three days, multiply by 30, and compare with the 10,000 monthly credits of Max. If the total is too high, run every other day, or move Reddit and X to a weekly run. If one run uses far more than you expect, check how much raw text it reads first.
A sample weekly report from today's data
With the instructions below, a teammate would turn the data from our 2026-11-22 calls into a report much like this one. Every number comes from the API responses above. We wrote the wording in the format of the instructions. Perplexity did not generate it.
Prices: among the four 1 kWh units, the Anker SOLIX C1000 Gen 2 and the DJI Power 1000 V2 were lowest at $469.99 each. Anker, BLUETTI and DJI all showed list prices, with discounts of about 33% to 41%. The Jackery Explorer 1000 v2 stayed at $559 with no list price and ranked number 2 in Outdoor Generators, behind Anker. New products: a STARYLINE 1 kWh unit appeared on page one at $339.99 with 9 ratings, at least $130 below the big four.
Discussion: the Jackery Japan account on X announced a Black Friday sale of up to 52% off on 2026-11-20 and a live stream on 2026-11-24. A post in r/Portable_PowerStation complained about Jackery after-sales service. Hiring: no new Jackery jobs this week.
This report has about 120 words. The model read a few dozen filtered fields and never read the 97,000 characters of raw LinkedIn text. The teammate's default model can write the report. The daily fetch and compare steps can use a cheaper model. The help center advises a stronger model for planning and hard decisions, and a faster, lower-cost model for routine work.
What the videos show, and what they skip
We searched youtube/search for "perplexity teammates", took the top three relevant videos, and pulled their subtitles with youtube/transcript. The 72-second video that Perplexity published (8S1XRdVXTYE) had 11,190 views on 2026-11-22. It covers the idea only: goals, parallel work, Slack, and automations. The 8-minute full guide (vC87aSkXeK0) gives five setup steps. Sign in on the web and name the teammate under Teammates.
Add plugins such as Slack, Gmail or GitHub. For GitHub, you can pick only some repositories. Then describe the workflow (where the work comes from, what to deliver, when to act), and assign it to a project with a first task. The third video (O1RM24jF_HE) covers plans only. It shows that yearly Max billing saves $400 over monthly billing, or 16.7%, and it notes that yearly billing is available only on the web.
None of the three videos shows how to connect a custom MCP server or API. None shows where the key lives or how many credits one run uses. The top 10 web pages for the keyword also stop at features and prices.
Sticking points on Reddit and forums
The r/perplexity_ai thread "Perplexity Teammates - worth it?" had 10 comments when we read it on 2026-11-22. One user runs an author business with it and is happy. Another advises against upgrading to Max for Teammates alone, unless you also want the other Max features. In the same thread, one user says that teammates have a separate usage allowance that is not unlimited. That user was down to 50%, and once it reaches 0%, teammate work starts to use credits (Reddit). This matches the video claim of free promotional usage, and it shows that the free part has a cap. In another thread, "Out Of Credits???", a Pro user who pays $20 a month got an email saying that their credits were gone. One reply says that this plan comes with no credits and that Computer needs purchased credits. After a few emails with support, the poster cancelled.
One reply says that 2,800 of 4,000 promotional credits expired unused and that support would not restore them (Reddit). Together, the two threads teach one lesson. Bonus credits expire in about 30 days, and the free teammate allowance runs out. A competitor watcher runs every day, so it needs a long-term credit budget.
Search suggestions show the same focus. Suggestions for "perplexity teammates pricing" add reddit, plans, guide, per month, enterprise, model and api. Suggestions for "perplexity teammates" add reddit, size, plan, account and pricing.
Most of them ask about price and plans. Only "api" asks how to connect outside data, which matches what the videos cover.
The Hacker News thread "Perplexity launches AI agents for work" (HN) mostly discusses whether Perplexity cites sources correctly. One comment recalls an old case in which every cited number was wrong. For competitor work, make the teammate cite the API field and time behind each number. A person can then spot-check the report.
Industry developments in the last 30 days
On 2026-11-06, Perplexity launched Teammates on the web. The same update added fully local Computer on the Mac and a new voice mode. Local mode needs an Apple-silicon Mac and is open to Pro, Max and Enterprise. Voice mode is for Pro and Max. These two features are separate from Teammates.
A local Computer is not a local teammate. On 2026-11-13, Teammates reached the Mac app (9to5Mac, TestingCatalog). Around 2026-11-17, the help center added a Teammates for Enterprise article. It says that Enterprise uses Enterprise Max seats and Computer credits, with no budget per teammate.
On 2026-11-18, the Perplexity Agent API changed its xhigh effort level to xhigh@2026-11-18.0, which uses openai/gpt-6.2-sol with no fallback model. To keep the old setup, pin xhigh@2026-11-11.0 (API changelog). If you build your own teammate, pin versions. Otherwise the cost and output of the same scheduled job can change.
Enterprise setup
Enterprise teammates need an Enterprise Max seat, and admins decide by role who can create them. A teammate uses the personal allowance of 15,000 credits a month first and then the org pool. You cannot set a budget for one teammate, and a teammate stops when its creator leaves. So a long-term member of staff should create a shared competitor teammate.
Give the competitive analysis team its own EveryInfra key and a spend limit set to the team budget. Monthly credit limits per SCIM group, from the changelog of 2026-07-27, are the nearest thing to a department budget on the Perplexity side.
Limits on data use
Competitor tracking uses public information only: prices and ratings on product pages, public job posts and public social posts. Each platform has its own data terms, such as the Reddit Data API Terms and the LinkedIn jobs terms. The official X API bills by posts read, at $0.005 each, with a cap of 3 million a month (X pricing).
A safe practice is to keep the report inside the team and quote only totals and links. Do not store or republish other people's text. The Perplexity Terms of Service also cover how Computer may access third-party services, so read them before production use.
Teammate instructions (configuration example)
Put the filter rules from above into the teammate's job. You can paste the block below into Advanced. We did not run it inside Perplexity, so it is a configuration example.
Role: Competitor watcher for portable power stations.
Competitors: Jackery, Anker, BLUETTI, DJI (ASINs listed in the project file).
Every day at 09:00 Singapore time:
1. Call amazon/profile for each ASIN. Record price, list_price, rating, rating_count, seller_name.
Report only if price or list_price changed since yesterday.
2. Call twitter/search with "<brand> since:<yesterday>" and reddit/search with "<brand>", sort newest.
Drop posts already seen (by id). Keep posts with more than 20 likes or any complaint.
3. On Mondays only: call linkedin/jobs with keyword "<brand>". Keep jobs whose company_name
equals the brand name, case-insensitive. If none, write "no new jobs".
4. If a call returns rate_limited, wait retry_after seconds and retry, at most 3 times.
If results are empty, say "no data" instead of guessing.
5. Post a 5-line summary to #competitors in Slack. Write a full report only on Mondays.
Never use tools other than everyinfra_call_api.
Step 1 reports only on change. Step 3 matches the company name exactly. Step 4 sets the retry rule. Each one comes from a case in the live calls.
Checklist before go-live
Before the teammate runs every day, do a one-day trial and check six items. Each item below comes from a case in our live calls. The trial costs a few cents in data fees and one day of credits. It is much cheaper than a month of wrong reports.
| Check | How to test | Pass |
|---|---|---|
| Auth | Call the catalog tool and one amazon/profile
|
Response has billing.charged_usd
|
| Filtering | Search jobs for "Jackery" on purpose | Joby Aviation is not in the report |
| Time window | Read the X keywords in the run log | Every keyword has since:
|
| Retries | Lower the per-minute limit for one run | Teammate waits and retries |
| Spend | Check the Usage page and the key spend | Both inside budget |
| Delivery | Read Slack for a week | Messages only on changes, full report on Monday |
What Teammates can and cannot do
| Can do | Cannot do, or not documented |
|---|---|
| Run on a schedule or on events, and keep a role and memory | Set a budget for one teammate (the Enterprise article says no) |
| Use installed plugins and connectors with your permissions | Add custom request headers in the connector form (except two Cloudflare Access headers) |
| Call any API through the vault, with the raw key outside the sandbox | Docs do not say which header the API Key mode sends |
| Use a different model per teammate | Publish a credit price per run (only task-level ranges) |
| Be tagged in Slack, GitHub and Linear | Run on Windows or Android (the product page says coming soon) |
FAQ
What does Perplexity Teammates cost?
Teammates has no separate price, but it needs Max: $200 a month or $2,000 a year, per the Perplexity help center on 2026-11-22. Teammate work uses Computer credits at 100 credits per dollar, and Max includes 10,000 credits a month.
Can I use Perplexity teammates on Pro?
No. The help center says that the research preview covers Max on individual and Enterprise plans only. Pro and Enterprise Pro are not included. A Pro user must upgrade to Max under All settings, Account, before creating a teammate.
How does Perplexity teammates pricing work for Enterprise?
Enterprise needs an Enterprise Max seat and bills in Computer credits. A teammate uses the personal allowance of 15,000 credits a month first and then the org pool. You cannot set a budget per teammate, and a teammate stops when its creator leaves.
Can a teammate connect to a custom MCP server?
The help center documents custom remote connectors with None, API Key or OAuth, for Pro, Max and Enterprise, and plugins can bundle MCP servers too. It does not say which request header the API Key mode sends. EveryInfra needs Authorization: Bearer. Add the connector and test it with one read-only call, or use the vault plus REST instead.
What does Reddit say about Perplexity teammates?
In the r/perplexity_ai "worth it?" thread, one user says that teammates have a separate usage allowance and start to use credits at 0%. In "Out Of Credits???", one user says that promotional credits expired before use. Keep daily runs light and send the full report once a week. The teammate can then stay inside the monthly Max allowance.
How is the Perplexity API different from Teammates?
The Agent API bills by model token, and MCP tool calls are free. You can narrow tools with allowed_tools and require_approval, and you write your own filter code. Teammates bill as Max plus credits and save you the scheduling work. Filters then live only in instructions or in scripts that the teammate writes.
Which model do Perplexity teammates use, and can I change it?
New teammates use Claude Opus 5.5 by default. You can pick a model for each teammate, and you can tell it to use different models for different tasks. Agents that a teammate starts use the same model unless you say otherwise.
How many teammates can one account have?
The help center says that you can create several teammates, each with its own job, and it gives no number. Teammates in the same Project share files and instructions and can message each other. For competitor work, split by platform.
One teammate covers Amazon prices and new products, and another covers X, Reddit and hiring. One of them writes the Monday summary.
Getting started
- Sign up in the EveryInfra console. Create a key for the teammate only, limit its capabilities, and set a spend limit.
- Check the capabilities in the API market. Start with Amazon Scraper API, Reddit Scraper API and LinkedIn Scraper API. Then see X Scraper API and TikTok Scraper API.
- Call
amazon/profileonce with the curl above, and check the fields andcharged_usd. - Follow the MCP server page to add
https://api.everyinfra.com/mcpto Perplexity (route A). You can also save the key in the vault (route B) or build with the Agent API (route C). - Paste the instructions into the teammate and run for one day. Check credit use before you set the final frequency. Work out the data fee from the pricing page and the
price_usdin the catalog.
Our article on Gemini Managed Agents with a remote MCP for brand monitoring uses the same data capabilities. Read it to compare how two agent platforms connect to them.
References
- Perplexity, Teammates, fully local Computer on Mac, and Voice mode, changelog, 2026-11-06
- Perplexity, Get started with Perplexity teammates, help center, read 2026-11-22
- Perplexity, Teammates for Enterprise, help center, read 2026-11-22
- Perplexity, Teammates, product page, read 2026-11-22
- Perplexity, Perplexity Max, help center, read 2026-11-22
- Perplexity, Max, purchase page, read 2026-11-22
- Perplexity, How credits work on Perplexity, help center, read 2026-11-22
- Perplexity, Adding custom remote connectors, help center, read 2026-11-22
- Perplexity, Using custom API credentials in Computer, help center, read 2026-11-22
- Perplexity, Create or upload a custom plugin, help center, read 2026-11-22
- Perplexity, Effort mode in Perplexity Computer, help center, read 2026-11-22
- Perplexity, Role-based access controls, API credentials, Brain for Max, changelog, 2026-07-27
- Perplexity, Ultrafast models, Decisions API, and connector controls, changelog, 2026-10-19
- Perplexity, Automations, inline visualizations, and GPT-6.1 Sol, changelog, 2026-10-05
- Perplexity, What we shipped, March 13, 2026, changelog
- Perplexity, Computer adds Automations for ongoing work, blog, read 2026-11-22
- Perplexity, Terms of Service, read 2026-11-22
- Perplexity Docs, MCP (Agent API tool), read 2026-11-22
- Perplexity Docs, Connectors, read 2026-11-22
- Perplexity Docs, Models, read 2026-11-22
- Perplexity Docs, Batch, read 2026-11-22
- Perplexity Docs, Effort, read 2026-11-22
- Perplexity Docs, Agent API quickstart, read 2026-11-22
- Perplexity Docs, Changelog, entry of 2026-11-18
- Perplexity Docs, Perplexity MCP Server, read 2026-11-22
- Model Context Protocol, Authorization, specification 2026-07-28
- Model Context Protocol, Security Best Practices, read 2026-11-22
- Model Context Protocol, Client Registration, specification 2026-07-28
- Model Context Protocol, Transports, read 2026-11-22
- Model Context Protocol, MCP Inspector, read 2026-11-22
- GitHub, modelcontextprotocol/inspector, read 2026-11-22
- IETF, RFC 6750: Bearer Token Usage
- IETF, RFC 9728: OAuth 2.0 Protected Resource Metadata
- IETF, RFC 8414: OAuth 2.0 Authorization Server Metadata
- IETF, RFC 7591: Dynamic Client Registration
- RFC Editor, RFC 8707: Resource Indicators for OAuth 2.0
- IETF, RFC 9700: OAuth 2.0 Security Best Current Practice
- IETF, The OAuth 2.1 Authorization Framework (draft 13)
- IETF, OAuth Client ID Metadata Document
- Cloudflare Docs, Service tokens, read 2026-11-22
- GitHub Docs, Managing your personal access tokens, read 2026-11-22
- Anthropic, Models overview, read 2026-11-22
- Reddit, Data API Terms, read 2026-11-22
- X Developer Platform, Pricing, read 2026-11-22
- X Developer Platform, Search Posts, read 2026-11-22
- Microsoft Learn, LinkedIn Job Posting API overview, read 2026-11-22
- LinkedIn, Jobs Terms and Conditions, read 2026-11-22
- Amazon Selling Partner API, Product Pricing API, read 2026-11-22
- EveryInfra, Data API catalog, read 12:41 Singapore time on 2026-11-22
- EveryInfra, Data API catalog, compact, read 2026-11-22
- EveryInfra, Amazon capability catalog, read 2026-11-22
- The Verge, Perplexity launches its own take on AI agents for work, November 2026
- The Verge, Anthropic takes on Muse with Claude Duet, 2026-10-21
- 9to5Mac, Perplexity brings AI agents feature called Teammates to the Mac, 2026-11-13
- TestingCatalog, Perplexity brings Teammates to Mac for Max subscribers, November 2026
- YouTube, Introducing Perplexity teammates, Perplexity, 2026-11-10
- YouTube, Master Perplexity Teammates for Your Business (Full Guide), subtitles read 2026-11-22
- YouTube, Perplexity Free, Pro or Max? Which Plan Gets Teammates?, subtitles read 2026-11-22
- Reddit r/perplexity_ai, Perplexity Teammates - worth it?, read 2026-11-22
- Reddit r/perplexity_ai, Out Of Credits???, read 2026-11-22
- Hacker News, Perplexity launches AI agents for work, read 2026-11-22
Originally published on the EveryInfra blog: Perplexity Teammates: pricing, and what competitor data costs. This article was written with AI assistance; the numbers come from the API calls and sources linked above, and were checked before publishing.
EveryInfra is a pay-per-call data API for AI agents and developers: everyinfra.com.



Top comments (0)