sas.com valid

SAS Developer Portal

The SAS Developer Portal (developer.sas.com) is the entry point for SAS Viya developer documentation, API references, OpenAPI specifications, SDK resources, and practical programming guidance.

For agents: SAS Developer Portal for SAS Viya: REST API catalog, OpenAPI specs, authentication guides, SDK resources and use-case examples.

sas viyarest apiopenapiauthenticationsdk

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T00:06:32.189Z. Cached copy · Source on sas.com

# SAS Developer Portal

The SAS Developer Portal (developer.sas.com) is the entry point for SAS Viya developer documentation, API references, OpenAPI specifications, SDK resources, and practical programming guidance.

## Getting Started

- [Full REST API index](https://developer.sas.com/rest-apis/index.md) - Start here for complete coverage: every publicly available API, grouped by product area, with links to each index.md and OpenAPI YAML.
- [REST API home](https://developer.sas.com/rest-apis) - Browsable landing page for the same catalog.
- [API quickstart and usage notes](https://developer.sas.com/docs/rest-apis/getting-started/usage-notes) - Learn request patterns, pagination, filtering, and common API conventions.
- [Use cases](https://developer.sas.com/usecases) - Browse practical implementation examples across SAS Viya topics.

## Authentication

- [Authentication guide](https://developer.sas.com/docs/rest-apis/getting-started/authentication) - Primary authentication and token acquisition guidance.
- [Auth guide for agents](https://developer.sas.com/auth.md) - Machine-readable OAuth 2.0 setup: token endpoint, grant types, scopes, and a worked curl example.
- [SAS Logon API](https://developer.sas.com/rest-apis/SASLogon/index.md) - OAuth protocol endpoints for obtaining access tokens, including client registration and scopes.
- [MySAS API keys dashboard](https://developer.sas.com/dashboard/api-keys) - Portal UI for API key management (requires sign-in).

## SAS Viya APIs

Each API links to its `index.md` - a machine-readable hub with the overview, full operations table, error codes, and links to that API's `authentication.md`, `usage-notes.md`, and raw OpenAPI YAML. Links resolve to the newest published version; use llms-full.txt to pin a specific one.
Follow an operation link in the API index to its detailed Markdown reference for parameters, request bodies, and responses. Do not guess operation IDs. Use the linked OpenAPI specification for additional contract details.
For a specific SAS Viya release (cadence), choose a published cadence listed in llms-full.txt. Append it after the complete Markdown path: `/rest-apis/{api}/index.md?cadence={cadence}` or `/rest-apis/{api}/{operationId}/index.md?cadence={cadence}`. Operation links preserve the selected cadence; do not silently switch releases when a requested cadence is unavailable.

### Visualization and Reports

- [Insights](https://developer.sas.com/rest-apis/insights/index.md) - The Insights API provides insights into your data.
- [Report Images](https://developer.sas.com/rest-apis/reportImages/index.md) - The reportImages API delivers SVG images representing elements of a report.
- [Report Transforms](https://developer.sas.com/rest-apis/reportTransforms/index.md) - This API creates and manipulates "transforms" of SAS reports that conform to the Business Intelligence Report Definition (BIRD) specification.
- [Reports](https://developer.sas.com/rest-apis/reports/index.md) - You can use the
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=sas.com · GET /v1/domain/sas.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for sas.com:
1. POST https://agentwebmap.com/v1/sites/sas.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://sas.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/sas.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/sas.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.