> For the complete documentation index, see [llms.txt](https://archer-bot.gitbook.io/archer.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archer-bot.gitbook.io/archer.bot/for-builders/partner-intent-telemetry.md). # Partner intent telemetry (V1) This page explains what the **My Agents** / intent detail UI is showing today. It is **not** the full outcome-weighted ranking engine (that formula exists in product docs but is only partially wired). Use this to interpret charts during dogfood and demos. ## Where you see it * **List:** `/developer/intents` — one row per `IntentDefinition` you own. * **Detail:** `/developer/intents/[id]` — charts, example queries, activate/test. ## Fees earned chart **What it measures:** Sum of **`providerCostMicro`** on `CreditTransaction` rows attributed to this intent over time (typically rolled up per day in the UI). | Concept | Meaning | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`providerCostMicro`** | Bob-reported fee in **micro-USD** (1 USDC = 1\_000\_000). Set when your endpoint returns `success: true` and includes `providerCostMicro`, or derived from flat-fee / `feeRate` rules on the Archer side. | | **When a row appears** | After a **successful** partner dispatch settles — not on failed tools, timeouts, or signature errors. | | **Who paid** | Alice's credit balance (or flat-fee on-chain path for Search **Run** / some partner flows). | | **Who receives** | Your `payoutAddresses` for the chain where the fee settled (flat-fee USDC on test is often Base Sepolia). | **What it is not:** Archer's TVR platform fee, LLM/infra CU charges, or on-chain gas — those live in other `CreditTransaction` component fields (`infraCostMicro`, `llmCostMicro`) and are not summed into "Fees earned." **Dogfood note:** on test, synthetic `CreditTransaction` rows with ids like `mock_telemetry_fee_*` are seeded so charts look populated without real traffic. ## Ratings chart **What it measures:** Aggregated **`MessageRating`** rows linked to messages where your intent was selected (`Message.selectedIntentDefinitionId`). | Concept | Meaning | | ------------- | ---------------------------------------------------------------------------------- | | **Source** | Alice (or tester) thumbs up/down (or score) on a chat message after your tool ran. | | **Scope** | Per **message**, attributed to the intent that produced the partner result. | | **Use today** | Qualitative feedback and future ranking input — **not** a payout trigger. | **What it is not:** the success-rate input to the ranking engine (that will use execution outcomes + volume windows). Empty charts simply mean no ratings yet. ## Ranking score (badge / Search ordering) **What you may see:** `rankingScore` on list/search cards (0–1). **V1 reality:** The **5-factor Search Score** (success rate, volume, sentiment, verification, stake) is defined in product docs but the **live ranking engine is not fully shipped.** Test/demo intents may have static or seeded scores. Treat displayed ranking as **directional UI**, not a contractual SLA. ## Invocation counts / TVR (future dashboard) Today, detailed "requests per window" and TVR for Bob are primarily in **admin/ops tooling and `CreditTransaction` + `Thread` history**, not a full self-serve Bob analytics dashboard. Each invocation still gets: * `requestId` in the signed envelope (dedupe + support) * `intentDefinitionId` on the message and ledger rows * Thread-level history for attribution When in doubt, ask Archer support for a `requestId` from a failed chat — that id ties together payment, dispatch, and partner logs. ## Publish / activate lifecycle (affects what telemetry includes) | State | Who can invoke | Search discovery | | ----------------------------- | -------------------------------------- | --------------------------------------------- | | **`isActive: false` (draft)** | **Owner only** (`ownerId` = your user) | Owner may see their draft if embeddings exist | | **`isActive: true`** | All authenticated users | Embeddings + semantic search | Inactive drafts **do not** generate public marketplace telemetry until activated (except your own tests). ## Related * [Publishing a Partner Intent](/archer.bot/for-builders/publishing-a-partner-intent.md) * [Pricing & Fees](/archer.bot/for-builders/pricing.md) * [Developer Portal](/archer.bot/for-builders/developer-portal.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://archer-bot.gitbook.io/archer.bot/for-builders/partner-intent-telemetry.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.