Dexscreener

Latest profiles

The trench feed asks Dexscreener for the latest token profiles and keeps the Solana ones. That request is how a cycle finds a concrete mint instead of a mood. Profiles are a list. The feed takes a recent slice, then asks for the pairs behind those token addresses so it can see which market the name is actually trading on.

This is a read, not a listing the desk controls. Dexscreener publishes profiles on its own clock. Agentra consumes the latest Solana slice when a cycle is thinking. If the read fails, the cycle does not invent a mint. The console can show that the loop was thinking, and the book waits for a later cycle that has a real pair.

The pair

Among the pairs that come back, the feed prefers a Pump.fun pair. A mint that ends in the pump suffix, or a market whose dex is Pump.fun or PumpSwap, belongs to the trench the agent is built for. The newest of those pairs, by when the pair was created, is the one the cycle buys.

Newest is a choice about the window. The trench is valuable while a name is still early. An older pair may still be liquid, and it is not what this loop is for. The sort is creation time, descending, and the first pair that survives the filter is the route. Solana explains why that pair’s mint is the contract you will see later.

The contract

The contract is the base token address on the pair. The feed keeps it only when it looks like a Solana address of the expected length and alphabet. A symbol is cleaned for the console so a wild name cannot break the line, and it is cut short enough to stay readable. The mint is not shortened in Activity. The row shows the contract in full so you can match it to the chain.

Buy and sell rows for the same cycle share that mint. If you page through Activity and see a buy of a symbol and a sell of the same symbol a moment later, compare the contracts. They should be the same string. That is the proof the close belongs to the open, not to a different name that happens to share a ticker.

On the desk

Dexscreener is also a public profile the project can point at once the Agentra pair itself is listed. The desk you use day to day is the command center, not the chart site. The chart site is where the outside world sees the pair. The feed is where the agent reads other pairs in order to work the vault.

When a profile, a social set, or a pair status changes on that public page, it does not rewrite the vault. The vault changes when a close settles. Keep those two clocks apart. One is the project’s public card. The other is the agent’s book.