> 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/publish-on-archer/partner-intent-telemetry.md).

# Your Earnings & Telemetry

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`** | Your 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. Failed tools, timeouts, and signature errors do not produce a row.                                                                                        |
| **Who paid**            | The user'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**    | A user (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 you are primarily in **admin/ops tooling and `CreditTransaction` + `Thread` history**, ahead of a full self-serve builder 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/publish-on-archer/publishing-a-partner-intent.md)
* [Pricing & Fees](/archer.bot/build-with-archer/pricing.md)
* [Developer Portal](/archer.bot/build-with-archer/developer-portal.md)