Observed
Price dislocation observed — cross-venue price, liquidity, market, and availability context recorded together.
sinsil.io / PRIMA
Cross-venue arbitrage intelligence, controlled before action.
PRIMA — the Price Routing Intelligence Market Aggregator — is the controlled cross-venue intelligence workspace of sinsil.io. It makes cross-venue price dislocations legible by reviewing price, liquidity, fees, transfer availability, timing, and operating constraints before any independently executed activity is considered.
PRIMA is the controlled workspace of sinsil.io — its cross-venue price-routing intelligence layer. Access is determined separately through named-user approval and relevant permissions.
The route, reviewed in order.
PRIMA separates observation, route qualification, and recordkeeping from any independently executed activity.
Qualified
Full route condition tested — estimated fees, depth, network status, timing, and reserve assumptions remain visible.
Reconciled
Evidence reconciled — independently documented outcomes may later be compared with the recorded condition.
PRIMA does not present price differences as advice, execution instructions, forecasts, or guaranteed arbitrage outcomes. Conditions may change materially between observation and independent action.
The workspace.
PRIMA is an intelligence workspace, not a public trading product.
It separates observation, route qualification, recordkeeping, and independently executed activity — presenting the route-observation and reference-analysis layer of sinsil.io.
Within PRIMA · records
Observation
Route qualification
Recordkeeping
Operating boundary
User assetsOutside the boundary — never held.
Records sit within PRIMA. User assets remain outside the boundary — PRIMA is not designed to receive, hold, or control them.
Outside PRIMA
Independently executed activityCarried out by the user, on their own accounts.
PRIMA focuses on whether a cross-venue price mismatch survives the full route: entry conditions, exit conditions, venue fees, withdrawal status, network availability, liquidity depth, estimated friction, timing, and capacity.
What PRIMA keeps visible.
PRIMA focuses on whether a cross-venue price mismatch survives the full route — entry and exit conditions, venue fees, withdrawal status, network availability, liquidity depth, estimated friction, timing, and capacity.
Cross-venue dislocation observation
Gross price variance is observed first — never represented as net value, an executable opportunity, or a probable outcome.
Net-route friction testing
Venue fees, withdrawal conditions, transfer availability, network costs, order-book depth, slippage reserve, and timing remain visible rather than implied.
Controlled reference qualification
A qualified reference condition is a time-bound label under stated assumptions — not financial advice, a recommendation, or a transaction instruction.
Evidence and variance reconciliation
Where an authorised user later submits a record, the purpose is variance review — not proof of repeatability, performance, endorsement, or future value.
“Evidence” refers to the traceability and completeness of an available record. It does not by itself mean that a result has been audited, independently verified, endorsed, or guaranteed.
Cross-venue intelligence.
How the workspace is put together — the route layer, the separation of concerns that keeps a record trustworthy, and the reference layer that lets coverage grow without changing how a route is reviewed.
Flexible routes
Speed and precision
A route is more than two prices. Entry venue, transfer path, exit venue, and network conditions are reviewed together, so a variance is examined as a complete path rather than a single number — and the assumptions behind it stay on screen.
Robust systems
Separated by design
Observation, route qualification, and recordkeeping are kept apart from independently executed activity. Each review leaves a traceable record, and access stays determined by named-user approval rather than open sign-up.
Scalable architecture
Customisable and extensible
PRIMA is structured as an aggregation and reference layer. Additional venues, transfer paths, and qualification criteria can be introduced without changing how a route is recorded, reviewed, or later reconciled.
Arbitrage intelligence.
A price mismatch is the start of an arbitrage case, not its conclusion.
PRIMA is built to distinguish a visible cross-venue variance from a route condition that remains intelligible after its full operating assumptions and constraints are considered.
Variance is observed first
Gross price variance is observed first; it is not represented as net value, an executable opportunity, or a probable outcome.
Friction stays visible
Venue fees, withdrawal conditions, transfer availability, network costs, order-book depth, slippage reserve, and timing remain visible rather than implied.
Qualification is time-bound
A qualified reference condition is a time-bound label under stated assumptions. It is not financial advice, a recommendation, or a transaction instruction.
Full-route condition checks
Entry venuePrice, fees, availability
Transfer pathNetwork, withdrawal, delay
Exit venuePrice, depth, fees
Market durabilityFreshness, volatility, spread decay
Capacity contextLiquidity, reserve, rebalancing
Reference framework
Bar lengths are illustrative proportions only. They are not a computation, a net value, a probable outcome, or a completed arbitrage result.
An observed mismatch becomes a useful reference condition only when all relevant inputs remain aligned at the time of review. It is not a completed arbitrage outcome.
Evidence and reconciliation.
The arbitrage case needs a clear chain of record.
PRIMA distinguishes a timestamped market observation from a reference route test, and from any independently documented outcome later submitted for review.
Observed dislocation
Timestamped venue prices, liquidity context, transfer availability, and source-category information are retained with the observation.
Reference route test
Estimated friction, reserve assumptions, route constraints, and qualification criteria are shown as part of the review record.
Independent outcome evidence
Where an authorised user later submits a record, the purpose is variance review — not proof of repeatability, performance, endorsement, or future value.
Built for controlled work.
The workspace is shaped around one rule — a condition is only useful if the record behind it survives review.
Designed for precision
A full-route review, not a headline number. Fees, depth, transfer availability, and timing are held together, so a variance is judged on its complete condition rather than on the gap between two screens.
Systems that adapt to the venue
Venue behaviour differs. Withdrawal states, network status, and order-book depth are read per venue, so a route is qualified against the conditions that actually apply to it.
Records that hold their shape
Every observation keeps its timestamp, stated assumptions, and source context — so an independently documented outcome can later be compared against what was actually recorded.
Engineered for growth
New venues, transfer paths, and qualification criteria can be introduced without changing how a route is recorded, reviewed, or reconciled. Coverage grows; the chain of record keeps its shape.
The platform makes conditions visible.
Each user retains account and transaction control. PRIMA is designed for controlled intelligence and recordkeeping workflows — it is not a public trading, custody, pooled-capital, or managed-execution service.
Institutional trust
No asset custody
Named-user access
No user asset custody
PRIMA is not designed to receive, hold, or control user assets.
No pooled user capital
User assets are not intended to be combined with one another or treated as operating capital.
No transaction authority
sinsil.io does not execute transactions or act on behalf of PRIMA users.
No exchange-credential collection
The intended access model does not require user exchange API keys, passwords, or account credentials.
No open PRIMA access
PRIMA access is determined through named-user approval and relevant permissions. Requesting access does not itself grant it.
No outcome promise
Observed variances, reference conditions, and scenarios are not advice, recommendations, forecasts, or guarantees.
Request submitted
Named-user review
Access decision
Go to PRIMA Console
Access is opened by named-user approval only. A request may be submitted for consideration and does not, by itself, grant PRIMA access. The present interface is a controlled concept preview using illustrative reference data.
sinsil.io / PRIMA
Proceed to PRIMA.
PRIMA is the directed application workspace of sinsil.io for authorised users. It presents cross-venue observations, reference route tests, qualification states, and evidence-reconciliation concepts under sinsil.io’s operating boundary.
PRIMA private workspace
Aggregation and reference layer
Named-user access controls
Access by request and approval only
No public route publication
Go to PRIMA Console
The present interface is a controlled concept preview using illustrative reference data. A live-observation or reconciled-evidence state requires validated inputs, operating review, route-condition confirmation, and a complete evidence workflow.