Perfect Corp · OAuth Scopes

Perfect Corp OAuth Scopes

OAuth 2.0 probed

Perfect Corp publishes 2 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Perfect Corp API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

BeautySkincareCosmeticsFashionApparelJewelryWatcheshairVirtual Try-OnImage EditingGenerative AIComputer VisionARvisual-commerceArtificial IntelligenceMachine LearningVideo Generationskin-analysisMCPAgentsPhoto EditingBeauty TechRetailar-try-onA2A

Scopes: 2 Flows: Method: probed

Scopes (2)

Scope	Description	Flows
task.run	Create and execute AI tasks. Inferred usage: the write half of the API — POST /s2s/v2.x/task/* and POST /s2s/v2.0/file. Perfect Corp publishes no scope description; the name is verbatim from scopes_supported.
task.read	Read task status and results. Inferred usage: GET /s2s/v2.x/task/*/{task_id} and the unit / feature-cost reads. Perfect Corp publishes no scope description; the name is verbatim from scopes_supported.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-02'
method: probed
source: https://yce-api-01.makeupar.com/.well-known/oauth-authorization-server
name: Perfect Corp YouCam API — OAuth 2.0 scopes
description: >-
  The 65 published OpenAPI documents declare only HTTP bearer security, so nothing OAuth-shaped is
  derivable from the contracts. The OAuth surface is discoverable instead at the RFC 8414
  Authorization Server Metadata document the API host serves anonymously, which names two scopes.
  Perfect Corp's prose documentation describes only the API-key bearer flow and does not document
  these scopes anywhere, so this artifact is the only public record of them.
docs: null
docs_note: >-
  No scopes / permissions reference page exists in the developer documentation. The scope names below
  come from the machine-readable metadata document, not from prose.

authorization_server:
  issuer: https://yce-api-01.perfectcorp.com
  metadata_url: https://yce-api-01.makeupar.com/.well-known/oauth-authorization-server
  metadata_file: well-known/perfect-corp-oauth-authorization-server.json
  authorization_endpoint: https://yce-api-01.perfectcorp.com/oauth2/authorize
  token_endpoint: https://yce-api-01.perfectcorp.com/oauth2/token
  registration_endpoint: https://yce-api-01.perfectcorp.com/oauth2/register
  grant_types_supported: [authorization_code, refresh_token]
  response_types_supported: [code]
  code_challenge_methods_supported: [S256]
  token_endpoint_auth_methods_supported: [none]
  client_id_metadata_document_supported: true
  note: >-
    A public-client profile — PKCE S256 mandatory, no client secret at the token endpoint, dynamic
    client registration (RFC 7591) open, and RFC 9728-style client-id metadata documents supported.
    That combination is the shape an MCP/agent client needs; the hosted MCP servers nonetheless
    authenticate with a static API key today and serve no /.well-known/oauth-protected-resource.

scope_count: 2
scopes:
  - name: task.run
    description: >-
      Create and execute AI tasks. Inferred usage: the write half of the API — POST /s2s/v2.x/task/*
      and POST /s2s/v2.0/file. Perfect Corp publishes no scope description; the name is verbatim from
      scopes_supported.
    grants: write
  - name: task.read
    description: >-
      Read task status and results. Inferred usage: GET /s2s/v2.x/task/*/{task_id} and the unit /
      feature-cost reads. Perfect Corp publishes no scope description; the name is verbatim from
      scopes_supported.
    grants: read

x-evidence:
  - url: https://yce-api-01.makeupar.com/.well-known/oauth-authorization-server
    http_status: 200
    content_type: application/json
    fetched: '2026-09-02'
  - url: https://yce-api-01.perfectcorp.com/.well-known/oauth-authorization-server
    http_status: 200
    note: The issuer host serves the identical document.
  - url: https://mcp-api-01.makeupar.com/.well-known/oauth-authorization-server
    http_status: 404

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/perfect-corp-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.